An idea about multi-process architecture
Why engage in multi-process architecture?
Each process has its own independent space, a process crashes, it will not affect other processes. Therefore, multi-process architecture program, which greatly enhanced robustness.
Single-process multi-threaded program, often encounter because the main thread stuck, resulting in the entire process "no reaction".
Compared with dynamic libraries DLL (BPL) framework What is the difference?
For dynamic library, hereinafter referred to as "bag."
For organizations that use package, called "plug-in" architecture.
For complex objects encapsulated packet or a 3rd party controls, often use "public package" encapsulating global (public) objects and variables.
Other packages to use a common object to be accessed by the public reference package.
In this way, when the program for deployment to runtime comes with many packages. For the package to bring this matter runs, many people are hated.
The multi-process architecture program, you do not have this trouble (with a run-time package is not required).
How to achieve multi-process architecture program?
The author of this provide an idea.
You can use the WINDOWS operating system's memory image file, the global shared objects between multiple processes.
Of course, this method also applies to bags and plug-in architecture shared among the global object plug-ins.
The specific implementation, see: https: //www.cnblogs.com/hnxxcxg/archive/2009/10/22/2940750.html