... | ... | @@ -2,8 +2,8 @@ In order to get automation within the Chronopolis Architecture we |
|
|
have a variety of messages sent with RabbitMQ for communication
|
|
|
between nodes. Messages are comprised of two parts, the header and
|
|
|
the body, each of which is mostly just key/value pairs. We will be
|
|
|
converting messages to JSON when transferring in case we move off
|
|
|
of Java in the future.
|
|
|
converting messages to JSON mostly for readability. We could just as
|
|
|
easily use MessagePack or ProtocolBuffers.
|
|
|
|
|
|
Exchanges
|
|
|
----------------
|
... | ... | @@ -76,5 +76,3 @@ Closed questions (can be reopened if needed): |
|
|
|
|
|
[1]: http://thoai-nguyen.blogspot.com/2012/05/rabbitmq-exchange-queue-name-convention.html
|
|
|
[2]: http://www.ietf.org/rfc/rfc4122.txt |
|
|
[MessageCreation]: https://adapt.umiacs.umd.edu/gitlab/chronopolis/chronopolis-core/wikis/MessageCreation
|
|
|
[MessageProcessors]: https://adapt.umiacs.umd.edu/gitlab/chronopolis/chronopolis-core/wikis/MessageProcessors |