Hm, if you "can have a layer of transactional components without COM+" - what d you use as DTC?
Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Peter Foreman [mailto:[EMAIL PROTECTED]] Sent: Montag, 13. Mai 2002 17:59 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Help Architecting A Middle Tier --- Thomas Tomiczek <[EMAIL PROTECTED]> wrote: > *** Resources. Like in Just In Tame Activation, like in Resource > Managers - I was talking of omputer resources. Given the memory overhead of a context in COM+, JITA is only worthwhile for objects that take up quite a bit of memory in terms of data. Given the largely stateless nature of COM+ it is unlikely that JITA saves memory for most objects. It is only worthwhile for 'large' objects, and even then pretty much only in combination with object pooling. (My personal opinion is that this explains why the JITA and object pooling interfaces were put together in IObjectControl. Originally they were designed to go hand in hand, because they only really make sense like that.) Writing an object pooling mechanism is fairly rare and not particularly hard in .Net. Connection pooling in ADO.Net is an example, where neither COM+ object pooling nor a COM resource dispenser was implemented. If MS are doing it - why don't we? > *** Try making componentized enterprise systems and then come back with > your opinion. There is hardly a match or replacement so far for MSMQ, > DTS etc. Sure, as long as you want to put every part of your logic into > the webpage, you are ok - but at one point the COM+ features come in > VERY handy. I've written componentized enterprise systems for the past 3 years with MTS/COM+. But .Net has changed the criteria with which I would use COM+. I'd use it or MSMQ under the right conditions, but with .Net I feel the right conditions will arise less than with ASP & COM. Designing systems with a transactional layer, such as COM+ enforces, is a good practice for developing large enterprise systems. Whereas COM+ used to be the best way of doing this, it is not the only way now due to the superior nature of component based development in .Net. You can have a layer of transactional components without COM+, and without the penalties of the past. 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.
