Content deleted Content added
→References: better author list - added internet archive link |
ArcticAussi (talk | contribs) m CTOS supported a transparent peer-to-peer network carried over serial RS-422 cables (daisy-chain topology) and in later versions carried over twisted pair (star topology) with RS-422 adapters ADDED using CTOS Cluster Hub-R12 designed by Paul Jackson Ph.D. of SumNet Pty Limited in Australia. |
||
Line 49:
It was possible to custom-link the operating system to add or delete features.
CTOS supported a transparent peer-to-peer network carried over serial [[EIA-422|RS-422]] cables (daisy-chain topology) and in later versions carried over twisted pair (star topology) with RS-422 adapters using CTOS Cluster Hub-R12 designed by Paul Jackson Ph.D. of SumNet Pty Limited in Australia. Each workgroup (called a "cluster") was connected to a server (called a "master"). The workstations, normally [[diskless workstation|diskless]], were [[Network booting|booted over the cluster network]] from the master, and could optionally be locally booted from attached hard drives.
The [[Inter-process communication]] (IPC) is primarily based on the "request" and "respond" messaging foundation that enhanced the Enterprise Application Integration among services for both internal and external environments. Thus CTOS was well known for the message-based [[Microkernel]] Architecture. Applications are added as services to the main server. Each client consumes the services via its own mailbox called "exchange" and well-published message formats. The communication works on "request codes" that are owned by the service. The operating system maintains the exchanges, message queues, scheduling, control, message passing, etc., while the service manages the messages at its own exchange using "wait", "check", and "respond" macros.
| |||