@Rajeev: There is a nominal cost to CF.CreateChannel (a few allocations if all you have is TCP or the out of the box NetTcpBinding). Note that if you are using Security or WS-RM sessions then you will be establishing a new security/RM session for each channel, as they don’t cache their sessions.

Thanks for the description of connection pooling.

I’m a novice user of WCF. Forgive me if my question is silly.

Is there a way to disable the “connection pooling” feature for buffered channels?

I’m interested in creating a unique tcp connection for each channel. Is there an alternative way to tell the framework to create a new TCP connection for every new channel? Specifically, any attributes/members in the netTCPBinding that I can tweak to achieve this?

Thanks.

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