Mach’s Networking

Since Rust uses the model of message passing (same as 202203021733) as a mean of thread synchronisation, a channel must be established for the threads to communicate with each other. The standard library std::sync::mpsc (mpsc stand for multiple producer single consumer#) provides the function mpsc::channel that could create a channel, which will define transmitter(s) (the one that sends messages) and receiver (the one that receives messages). The return type will be a tuple, the first element represents transmitter(s), the second element represents receiver. Combining with #202207171541, we can send a message from a thread (via transmitter’s method send) to the main thread (via receiver’s method recv or try_recv).

Mach enforces that all objects to be local independent and transparent to the user. This means that all #message passing could be done or seems to be done locally. The **messages#** passed will contain typed data objects, which compared to alternative where data in them will be untyped streams of bytes, are easier to parse even if the byte ordering is different from the sender and receiver.

See 202203021733#

There are error handlers, one for each thread, in Mach. The thread and its error handler will communicate using message passing#, and the handler will decide whether to resume or terminate the thread.

Go uses message-passing as the basis for 202207171457 like #rust and 202203021733.