serai/message-queue
Luke Parker 571195bfda
Resolve #360 (#456)
* Remove NetworkId from processor-messages

Because intent binds to the sender/receiver, it's not needed for intent.

The processor knows what the network is.

The coordinator knows which to use because it's sending this message to the
processor for that network.

Also removes the unused zeroize.

* ProcessorMessage::Completed use Session instead of key

* Move SubstrateSignId to Session

* Finish replacing key with session
2023-11-26 12:14:23 -05:00
..
src Resolve #360 (#456) 2023-11-26 12:14:23 -05:00
Cargo.toml Move message-queue to a fully binary representation (#454) 2023-11-26 11:22:18 -05:00
LICENSE Add a message queue 2023-07-01 08:53:46 -04:00
README.md Add a message queue 2023-07-01 08:53:46 -04:00

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.