ASP and MTS - where is best place to start a transaction

[Rob Richards]

Does anyone know of any trade offs by using a Transaction within the
ASP page rather than having the ASP page with no transaction support
directly call an MTS object and having the object perform all the
transactional functions.

I was under the impression that there should be little to no business
logic with the ASP page other than for display purposes yet also have
heard others talk about using the Transaction tag in the ASP page and
calling a bunch of MTS objects using the ASP page as the base of the
transactions.

Does anyone have any ideas on this?

Thanks,

Rob

[Cowboy]

On Thu, 04 May 2000 12:46:07 GMT, rric...@pivot.net (Rob Richards)
wrote:

In Windows DNA, you can have a transaction start at any point. Since I
tend to move as much buisness logic to components, I see no reason for
the ASP to participate in the transaction. However, there are times
when there is logic in the ASP that you are not given time to move to
components. In these instances, I can see using an ASP transaction.
There may be other instances, like part of the logic being in a Java
Applet or ActiveX control. I cannot see why this would be done at
present, but each person codes a bit different.

GB
MCP+I, MCSE, MVP
**********************************************************************
Think outside the box!
**********************************************************************

[Rob Richards]

Thanks,

I too follow your same train of thought. I was just a little thrown
when I saw some "Gurus" in this area showing examples where they
initiate the transaction in the ASP page where it clearly would not
need to be (especially in their example). Not being able to get an
answer from them I was a little confused why they would choose to do
this. It may have been for example only.

Anyways, thanks again. Just making sure I wasn't off base anywhere.

Rob