I am trying to discern the difference between SingleCall and Singleton activation methods when implementing a server to host an object using .NET Remoting. It would appear that SingleCall has the overhead of having to construct and clean up an object for each client-side call, whereas Singleton has the limitation of only being able to service a limited number of simultaneous requests. I am looking to make performance as good as possible. Which should I choose?
I am trying to discern the difference between SingleCall and Singleton activation methods when
Share
By default, you should use SingleCall.
Also, keep in mind that, when using SingleCall objects, you cannot share state accross calls.
I found this site a good resource when it comes to .NET remoting: http://www.thinktecture.com/resourcearchive/net-remoting-faq/remotingusecases