I have a singleton object that's accessed via remoting by way of
Activator.GetOb ject():
SomeObject
someObj=(SomeOb ject)Activator. GetObject(typeo f(SomeObject),s omeUrl);
My question is: Is the proxy returned by Activator.GetOb ject() thread-safe?
I know that my IMPLEMENTATION of SomeObject has been built in a thread-safe
way -- but is the PROXY generated by GetObject() thread-safe?
In other words, if I create the 'someObj' proxy at startup, can I safely
make method calls against it from multiple threads?
Thanks,
Jules
Activator.GetOb ject():
SomeObject
someObj=(SomeOb ject)Activator. GetObject(typeo f(SomeObject),s omeUrl);
My question is: Is the proxy returned by Activator.GetOb ject() thread-safe?
I know that my IMPLEMENTATION of SomeObject has been built in a thread-safe
way -- but is the PROXY generated by GetObject() thread-safe?
In other words, if I create the 'someObj' proxy at startup, can I safely
make method calls against it from multiple threads?
Thanks,
Jules