WCF ChannelFactory and Channel caching in ASP.NET client application?

Ideally close the channel as soon as you are done with it. This will place it back into the channel pool so it can be used by another worker thread Yes, the channel factory (the expensive bit) can remain for the lifetime of the application.

Ideally close the channel as soon as you are done with it. This will place it back into the channel pool so it can be used by another worker thread. Yes, the channel factory (the expensive bit) can remain for the lifetime of the application.

– tucaz Dec 1 '09 at 14:25 One channel factory per service type, correct. This way you don't have to do all the reflection and type creation every call, which is why for performance you shouldn't use the proxy generated by VS as the class is gens uses a new factory every call. – MattC Dec 1 '09 at 16:59 "you shouldn't use the proxy generated by VS as the class is gens uses a new factory every call" - according to the link at the end that particular problem was solved with .

NET 3.5 so that ChannelFactory is cached within ClientBase. Blogs.msdn.Com/wenlong/archive/2007/10/27/… – Xiaofu Dec 1 '090 at 15:45.

This is an aside. Why are you using SessionID as a context key? The context.

Items is unique per request. That is: HttpContext.Current. ItemsHttpContext.Current.Session.

SessionID +"_ListOfOpenedChannels" should be functionally equivalent to: HttpContext.Current. Items"ListOfOpenedChannels".

I realized that after I posted this question. The final result is here: github. Com/tucaz/CommunicationsManager Thanks – tucaz Mar 4 '10 at 11:09.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.