well, it's more of a concern of how much overhead is involved and what is more efficient, the overhead of creating new objects each time, or the overhead of using System.EnterpriseServices in general ( to use object pooling). I do not know about it enough, so I am reading Derek Beyer's book "C# COM+ Programming" to hopefully answer my questions. Mainly I would just be curious for someone to explain how the overhead of com+ is laid out, and whether the only way to find out which to use is trial and error and see which method performs better, or if there is a standard rule when to and when to not use it.
thanks. On Wed, 26 Jun 2002 17:02:30 -0400, Marsh, Drew <[EMAIL PROTECTED]> wrote: >Jeff Mangan [mailto:[EMAIL PROTECTED]] wrote: > >> We are interested in using object pooling, and it looks like >> the only thing I have found is using >> System.EnterpriseServices and Com+. Is this enough >> justification for using it, or how can we determine if there >> will be more overhead in using System.EnterpriseServices then >> we will have by instantiating the object over and over again. >> I keep hearing "do not" use >> com+ services unless you absolutely have to, but if we want object >> com+ pooling >> for c# assembilies, is this enough reason to use it?? > >Aboslutely. Out of curiousity, is there any more context around the warnings >for "do not use com+ services unless you absolutely have to"? What are the >people warning you afraid of? Just curious. > >Later, >Drew > >[ .NET MVP | weblog: http://radio.weblogs.com/0104813/ ] > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
