Hi, I've been puzzling over a .NET Remoting question....
With a Singleton object over .NET Remoting, I assume that every client gets a chance to access the same instance of the object, using a thread from the runtime's pool. Thus, if the Singleton object holds any state, lock statements and the like need to be used to ensure it can be used without problems. However, if the object is stateless, is there really any locking or concurrency concerns to worry about? And would a stateless Singleton object perform more or less the same as a stateless SingleCall object in this case? Any thoughts appreciated, Matthew You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
