SAO Singleton - Multiple Instances?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I've got a server activated object (SAO), in singleton mode (hosted in a server Console application on same machine as client). On the client, I can instantiate serveral instances via Activator.CreateInstance, and each instance maintains its own state correctly (via properties on the object). This is what I want! However, it's not the way I understand and read that Singletons are supposed to work (all mention of it indicates that state will be shared across ALL instances).

Can anyone confirm that I can rely on this stateful type of operation?

Thanks.

P.S. I'm using .NET 2.0.

.

Relevant Pages

  • Re: Design question
    ... Usually a server activated object setted as a singleton will create ... The default lifetime is 5 minutes I think, ... Your instance of the object is created by the client? ...
    (microsoft.public.dotnet.framework.remoting)
  • RE: Well-known server activated object and IDisposable
    ... My question can be formed in a differnet way...: ... How can I know from inside a function in the well-known server activated object that it has been called from the client or it has been called from the hosted server? ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)