COM+ architecture question
-
The project I'm working on is moving from good old DCOM to COM+. I find it hard to solve one issue. Back in DCOM days, when you had data that had to shared by all the objects of a class, there was no problem holding inside the DCOM EXE server and letting all instances know of it (data such as a list of connected currently connected users, etc). How do I do it in COM+, as all objects are created through surrogate DLLs ? Thanks, Omer.
-
The project I'm working on is moving from good old DCOM to COM+. I find it hard to solve one issue. Back in DCOM days, when you had data that had to shared by all the objects of a class, there was no problem holding inside the DCOM EXE server and letting all instances know of it (data such as a list of connected currently connected users, etc). How do I do it in COM+, as all objects are created through surrogate DLLs ? Thanks, Omer.
If you are using a C++ server, it's simple, it's just a matter of creating a global DLL variable. If you want to use the COM+ way, or for VB DLLs, you can use the Shared Property Manager (SPM), which is designed exactly for this. I see dumb people
-
If you are using a C++ server, it's simple, it's just a matter of creating a global DLL variable. If you want to use the COM+ way, or for VB DLLs, you can use the Shared Property Manager (SPM), which is designed exactly for this. I see dumb people
-
I need a whole Data structure (and not a simple one). If I understand correctly, what you suggest is to wrap it up with COM and pass it around to all instances this way or another. Isn't there a simpler solution ?
No you don't need to wrap it with a com object, simply you need to keep your data structure as a global variable to the dll module then provide a code that manipulate that structure with a multi-threaded-safe fasion and you are done. if you want to avoid writing syncronization code you can rely on the sahred property manager as daniel advised. AbuMalek