Re: 20 seconds before socket is closed.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



On 9 Aug, 22:09, UL-Tomten <tom...@xxxxxxxxx> wrote:
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

Hi

I've done this already and it is not relevant. It has no bearing on
when the socket is closed.

Thanks for you help.
Justin

.



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. ... Look up the documentation for InitializeLifetimeService on MSDN: ...
    (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)