Comments on: Client (TCP and Named Pipe) Connection Pooling http://kennyw.com/indigo/173 Kenny Wolf's Thoughts of the Moment Thu, 20 Nov 2008 15:46:07 +0000 http://wordpress.org/?v=2.2.2 By: More details on MaxConnections at kennyw.com http://kennyw.com/indigo/173#comment-51897 More details on MaxConnections at kennyw.com Sat, 02 Jun 2007 21:44:06 +0000 http://kennyw.com/indigo/173#comment-51897 [...] TCP is not a hard and fast limit, but rather a knob on the connections that we will cache in our connection pool. That is, if you set MaxConnections=2, you can still open 4 client channels on the same factory [...] […] TCP is not a hard and fast limit, but rather a knob on the connections that we will cache in our connection pool. That is, if you set MaxConnections=2, you can still open 4 client channels on the same factory […]

]]> By: Yuri Kozlov http://kennyw.com/indigo/173#comment-42833 Yuri Kozlov Tue, 24 Apr 2007 07:17:16 +0000 http://kennyw.com/indigo/173#comment-42833 Hallo Kenny, I have one question concerning porting Remoting to WCF. I my Remoting-based application i used now and then the Remoting's capabilities to immediately marshal interfaces; this means, i can pass interface of client's object to the server, store this interface reference at server side in some variable, and later call back from server to the client through this interface refernece. All i need is to derive client's class from MarshalByRefObject and normally to overwrite InitializeLifetimeService() so that the latter returns null. What is the best way to port this code to WCF? I notice that i cannot pass the interface reference as remote method's parameter in WCF : WCF ignores MarshalByRefObject and tries to serialize the client's object whose refernce is passed. All my server objects are SingleCall activated and i want this to stay, which means i cannot do WCF sessions. Do i need Duplex functionality for this or is there some other way to marshal interfaces' references? Thank you in advance. Yu. Kozlov Hallo Kenny,

I have one question concerning porting Remoting to WCF.

I my Remoting-based application i used now and then the Remoting’s capabilities to immediately marshal interfaces; this means, i can pass interface of client’s object to the server, store this interface reference at server side in some variable, and later call back from server to the client through this interface refernece. All i need is to derive client’s class from MarshalByRefObject and normally to overwrite InitializeLifetimeService() so that the latter returns null.

What is the best way to port this code to WCF? I notice that i cannot pass the interface reference as remote method’s parameter in WCF : WCF ignores MarshalByRefObject and tries to serialize the client’s object whose refernce is passed. All my server objects are SingleCall activated and i want this to stay, which means i cannot do WCF sessions. Do i need Duplex functionality for this or is there some other way to marshal interfaces’ references?

Thank you in advance.

Yu. Kozlov

]]>