Good :-) So if I make a component that MIGHT be used in a transaction with others (which, btw,, imho is more or less a requirement if you make "building blocks"), then it IS COM+ :-)
Imagine your business component suddenly being "steered" from a component taking orders out of a message queue? You suddenly have to participate in a third party transaction. Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Peter Foreman [mailto:[EMAIL PROTECTED]] Sent: Montag, 13. Mai 2002 22:48 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Help Architecting A Middle Tier --- Thomas Tomiczek <[EMAIL PROTECTED]> wrote: > Hm, if you "can have a layer of transactional components without COM+" - > what d you use as DTC? Firstly, if you have multiple RMs then I'd go with COM+/DTC. However, the DTC is considerable overhead in the single RM case. Code transaction start/end points in stored procedures or in ADO.Net code. Peter __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
