> However, if the object is stateless, is there really any > locking or concurrency concerns to worry about?
No. Same as with any object. Of course, the reverse is also true: just because you're using a SingleCall object doesn't mean you *don't* have to worry about concurrency - think about static fields. > And would a > stateless Singleton object perform more or less the same as a > stateless SingleCall object in this case? The one difference is that a SingleCall object will be garbage at the end of the call. So if you're expecting a large number of calls, Singleton may actually perform better due to less frequent GC cycles. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
