Guest_imported
New member
- Jan 1, 1970
- 0
I am learning COM and one thing that my books do not explain is if a loaded (in memory) component can generate objects for multiple applications and/or clients.
In other words assume that app1 inititalizes com and then requests object1. I would assume that COM would find and load the component and then the class factory would be used to create the object and provide an interface pointer back to app1.
But what if app2 wanted to use the very same object. Would COM:
1. Find and load another instance of the COMPONENET in memory and use it to generate another obhject instance?
2. Use the existing loaded COMPONENT to generate another object instance.
3. Use the already instantiated object1 but perhaps provide a separate data space? I think this used to be referred to as re-entrant but I'm not sure with COM terminology.
I suspect that the location of app2(in-process, local, or remote with regard to app1) might affect this and perhaps some of the properties specified when the COM server is designed but I'm not sure.
Thanks for any assistance.
In other words assume that app1 inititalizes com and then requests object1. I would assume that COM would find and load the component and then the class factory would be used to create the object and provide an interface pointer back to app1.
But what if app2 wanted to use the very same object. Would COM:
1. Find and load another instance of the COMPONENET in memory and use it to generate another obhject instance?
2. Use the existing loaded COMPONENT to generate another object instance.
3. Use the already instantiated object1 but perhaps provide a separate data space? I think this used to be referred to as re-entrant but I'm not sure with COM terminology.
I suspect that the location of app2(in-process, local, or remote with regard to app1) might affect this and perhaps some of the properties specified when the COM server is designed but I'm not sure.
Thanks for any assistance.