Hi, El vie, 01-09-2006 a las 14:53 +0100, Bradley, Peter escribió: > Just a query... > > Why do you need to use a singleton object? We've always used SingleCall > objects, and these die after each call. I take it you're talking about a > SAO, as the term "singleton" is usually used to refer to an SAO. We've never > found a justification for using a singleton object. >
And what happend when you want to have (in server side) a shared struct or shared hash hosted in memory for all calls?. For example to keep an array of client sessions at the server. Do you prefer a SingleCall object with static variables instead of singleton object? Thanks -- Carlos Ble Shidix Technologies www.shidix.com/carlosble _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
