4 commits

Author	SHA1	Message	Date
Luke Parker	8543487db2	Document message-queue RPC methods	2023-07-16 20:53:58 -04:00
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
Luke Parker	b0c28a1cf0	Move message_queue over to deduplication via intents ... 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).	2023-07-16 20:34:35 -04:00
Luke Parker	6267acf3df	Add a message queue ... This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.	2023-07-01 08:53:46 -04:00