WCF CreateChannel for every method call

In my current web project, we perform a ClientFactory.CreateChannel for every method call to a re开发者_Go百科mote service.

Is this really necessary? What is the best practice?

---

This depends to some extent what your requirements are. Opening a channel is expensive, relatively speaking. Best practice is to have the class that is doing the remote calls implement IDisposable, it should make a call to ClientFactory.CreateChannel once, use the channels in all the method calls, and close the channel when the Dispose method is called. That said, if the time between the calls to methods that call to a remote service is long (longer then the default idle timeout on the channel which is 10 minutes) then doing a ClientFactory.CreateChannel isn't particularly harmful, but I would say it would still be better to go the IDisposable route and encapsulate use of the class with the 'using' keyword

---

creating a new channel for each method call comes in bad practice "generally".

For Duplex WCF Service

creating a single channel and using it until there is no need to communicate with server anymore/ or that channel gets closed.

After creating the channel, before making any call to server, its recommended to check channel's state (Error, opening, closed).

Registering the channel closed/Error events is recommended to get to know immmediatley when it occurs. so you can take necessary actions or/and create the channel again with same object channel object reference.

For Normal WCF service

Create the proxy pattern, to create channel/ to re-use/ re create, error handling and disposing. set the appropiate inactivity timeout along with WCF client's proxy appropiate configuration which suits best with your solution.

Always Load test!!!!