mirror of
https://github.com/serai-dex/serai.git
synced 2024-12-22 11:39:35 +00:00
b0c28a1cf0
Due to each service having multiple distinct clocks, we can't expect a stable ordering except the ordering an intact message-queue provides. The messages emitted should be consistent however, solely with unknown order, which is why we can craft intents based on their contents (already implemented by processor-messages). |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
LICENSE | ||
README.md |
Message Log
A message log for various services to communicate over.
Each message is checked to be of the claimed origin. Then, it's added to the recipient's message queue. This queue is sequentially handled, FIFO, only dropping messages once the recipient acknowledges it's been handled.
A client which publishes an event specifies its own ID for the publication. If multiple publications with the same ID occur, they are assumed repeats and dropped.
This library always panics as its error-cases should be unreachable, given its intranet status.