This may help you:
http://www.csharphelp.com/archives2/archive422.html
However, I would advise against relying on the data in singleton objects,
even if you set their lifetimes to be infinite. The problem is that any
changes made by one client affects all the other clients. You may think
this is fine for the clients you are using - but when some other programmer
uses your object, difficulties may arise. It makes much more sense to use
client activated objects if you want to persist remote object state.
However, I have not yet found a situation where I could not manage with
stateless objects, and I always use either SingleCall SAOs or Web Services.
This fits in much better with a service oriented architecture.
Just my 2c. YMMV.
HTH
Peter
"Mahesh Deo" <MaheshDeo (AT) discussions (DOT) microsoft.com> wrote
Quote:
Hi
i have a singleton(server activated) remote object and a client app which
calls mothods of remote object. but after 5 minutes the remote object
stops
working.So what should i do to keep that remote object serving to clients
till the server is on and runnig.
Thanks you. |