serai/message-queue
Luke Parker a9072e6b1b
Remove signature from get_next_message
Duee to signature replaying, it's very annoying to provide meanigful data
access privacy. None of these messages should be private/have sensitive data
anyways though.
2023-07-16 20:38:13 -04:00
..
src Remove signature from get_next_message 2023-07-16 20:38:13 -04:00
Cargo.toml Move message_queue over to deduplication via intents 2023-07-16 20:34:35 -04: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.