Jeff Mangan [mailto:[EMAIL PROTECTED]] wrote:
> 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
t;
>-Original Message-
>From: Jeff Mangan [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, June 26, 2002 2:43 PM
>To: [EMAIL PROTECTED]
>Subject: Re: [DOTNET] object pooling
>
>well, it's more of a concern of how much overhead is involved and what
>is
>more efficient,
PROTECTED]]
Sent: Wednesday, June 26, 2002 2:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] object pooling
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.EnterpriseServic
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# C
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
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
instantia
