--- Thomas Tomiczek <[EMAIL PROTECTED]> wrote: > (a) Transaction support and propagation.
In a multiple resource manager/DTC case - agreed. But in the simple case of a single RM it's probably not worth the overhead of DTC compared to hand coding the transaction start and end points, especially if you are implementing data manipulation code in stored procedures. > (b) security. Are we talking about call security, or role based security. Role based security is something I have yet to find a real use for. > (c) resource optimization. What resources? COM+ introduces a number of areas of overhead in terms of time and memory. > For the next years, Remoting is not a competitor to DCOM, sorry. In the old ASP/COM world scripting ASP is poor compared to components in VB/VC++ in terms of error handling, debugging support etc. Since you're going to the effort of coding up components, you might as well go the extra mile to COM+ and get the extra features for relatively little additional effort. However, with ASP.Net there is less of an incentive to go down this route since the coding model in ASP.Net is first class. I really see COM+ being much less important in .Net. Peter Foreman __________________________________________________ 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.
