aether
aether copied to clipboard
dtqec
Distributed system emulation in Common Lisp
When the convenience keyword `:replies?` is flagged, `send-message-batch` registers a mailbox per message to use as a reply repository. This keyword currently defaults to `t`, since `send-message-batch` is almost everywhere...
Only the termination condition seems tricky to sort out.
Except for readability, this isn't really used — and it's not even clear how useful it is for readability.
If `receive-message` is called repeatedly on a given inbox, it may fruitlessly search through a large head of messages many times. Instead, one might maintain a pointer (per message type)...
In `network.lisp`, one finds the following comment: ``` ;; IMPORTANT NOTE: On reflection, a nondeterministic routing strategy will mean ;; that it's possible for violate message delivery order, which is...
`spawn-process` presently (1) creates a process object and (2) registers it in the dereferencing table. This is a bit shy of what "spawn" means in other actor frameworks, where the...
In application code, we have a family of generic get/set messages, as well as a `->` macro which performs repeated de/referencing. I would like aether to own these message definitions...