LostProgrammer
Well-known member
- Joined
- Jan 17, 2003
- Messages
- 123
Assumptions:
1) Single Call remote objects are ideal because they are stateless and will be destroyed after each method call
2) Activator.GetObject does not return the newly created object, only a proxy to the object
If anyone can dispute these with documented proof please do, because there seems to be ambiguous info on remoting in .net.
So, if the above are true , then ideally, wouldnt you call activator.getobject to create a new instance of the remote object each time you needed to call a method of that object?
None of the examples or docs that i have seen state this directly. Is this true? Activator does not generate a a network call so there is no need to pass the r.o between forms or hold a reference in a class member.
Thanks for any comment,
-lp
1) Single Call remote objects are ideal because they are stateless and will be destroyed after each method call
2) Activator.GetObject does not return the newly created object, only a proxy to the object
If anyone can dispute these with documented proof please do, because there seems to be ambiguous info on remoting in .net.
So, if the above are true , then ideally, wouldnt you call activator.getobject to create a new instance of the remote object each time you needed to call a method of that object?
None of the examples or docs that i have seen state this directly. Is this true? Activator does not generate a a network call so there is no need to pass the r.o between forms or hold a reference in a class member.
Thanks for any comment,
-lp