The current thinking on process management is the use of a four-level system, as follows:
- Partition. Processes in one partition cannot, under any circumstances, view or identify processes in another partition, with the exception of Driver Processes and processes in the administrative partition. It may be possible to allow one partition to grant access to another partition, or for child partitions, instead of or in addition to the admin partition method. I'm yet undecided on this one. Partitions are designed to allow a system to act as a host for various "virtual machines", supported directly at the kernel level.
- Session. Processes in a session can control each other and/or communicate with each other. Sessions are used by the dispatcher to group resources in process groups.
- Process. The process boundary generally extends to encompass an entire application.
- Subprocess/thread. The subprocess and thread level encompasses both light-weight (memory-sharing) threads and copy-on-write threads within a single application.
All pages in this group are proposals for the Cy/VOS NG experimental prototype. They form an official roadmap for the development of this prototype and the technologies involved, but the prototype itself is NOT DESIGNED FOR USE.
While many of the technologies described herein may have applicability, presense here is not a sign that they will eventually be in Cy/VOS.
