Sorry for the very basic question
I am asking a noob question about remoting cos I am unsure how remoting works
in terms of tcp connection.
I am comparing remoting Vs network programming (tcp sockets):
The scenario is App A send a data to App B:
1) For network programming,
App A -> make a socket connection to App B.
Once connection established, App A send data to App B.
App A tear down connection when done.
For remoting, how does App A make a socket connection to App B
Throughout the lifetime of the applications Or is it similar to network programming
such that the tcp connection will be teared down
I am checking whether remoting will be wasting network resources by keeping the tcp connection alive
Thanks!!
Sorry for the very basic question
Siza
Hi i_luv_peanuts, with the TcpChannel in the .NET Framework 2.0, the underlying connection will be created when you make a remoting call, and then a timer will be started. If the timer expires before you make another call, the connection is torn down. If you make another call before the timer expires, the timer is reset and starts counting down. This way the connection will stay up if you keep using it.
You can set the timeout directly if you'd like more control, and we also give you the option of using an absolute timeout, which tearns down a given number of seconds after the connection is opened, regardless of whether more calls are made on it.
Hope that helps.
JJustice [MSFT]