Re: 20 seconds before socket is closed.

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: UL-Tomten <tomten@xxxxxxxxx>
Date: Thu, 09 Aug 2007 14:09:10 -0700

On Aug 3, 5:19 pm, Justin__Bar...@xxxxxxxxxxx wrote:

I've been asked to find out why it takes 20 seconds before the socket
is closed after a call to a SAO singleton or singlecall object. Is it
possible to change this idle time figure?

Technically that's not idle time, that's the channel living its life.
I bet you would take offence if someone was asked to find out why it
took 90 years for Justin to dispose.

Look up the documentation for InitializeLifetimeService on MSDN:
http://msdn2.microsoft.com/en-us/library/4th828yf.aspx

.

Follow-Ups:
- Re: 20 seconds before socket is closed.
  - From: Justin__Barnes

References:
- 20 seconds before socket is closed.
  - From: Justin__Barnes

Prev by Date: Re: SAO Singleton - Multiple Instances?
Next by Date: Re: SAO Singleton - Multiple Instances?
Previous by thread: 20 seconds before socket is closed.
Next by thread: Re: 20 seconds before socket is closed.
Index(es):
- Date
- Thread

Relevant Pages

Re: 20 seconds before socket is closed.
... is closed after a call to a SAO singleton or singlecall object. ... Technically that's not idle time, that's the channel living its life. ... when the socket is closed. ...
(microsoft.public.dotnet.framework.remoting)
Re: 20 seconds before socket is closed.
... is closed after a call to a SAO singleton or singlecall object. ... Technically that's not idle time, that's the channel living its life. ... when the socket is closed. ...
(microsoft.public.dotnet.framework.remoting)
20 seconds before socket is closed.
... I've been asked to find out why it takes 20 seconds before the socket ... is closed after a call to a SAO singleton or singlecall object. ... possible to change this idle time figure? ...
(microsoft.public.dotnet.framework.remoting)