Skip to content

Finalize multi-part message components #18

@jmader

Description

@jmader

The first order of business is to make sure the message contents described here are what we need:

https://keckobservatory.github.io/mKTL/protocol.html#request-response

A related unresolved question is whether the field ordering should be aligned between PUB messages and REQ/REP messages. The topic must be the first field of a PUB message; this is the 'target' as described in the documentation. It could be put first for all the messages, followed by the version number, and etc. etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions