I'd like us to adopt a convention where the payload for messages, incoming and outgoing, is expected to be conformant JSON. I currently have to adopt a string parser to read parts of the responses, to determine how to dispatch.
The semantics of the JSON is something we can discuss in a separate ticket. For example, a number of systems expect messages to be organized into "channels". We could do that in the payload, or we could later do that in the websocket URI. But that can be a different discussion.
I'd like us to adopt a convention where the payload for messages, incoming and outgoing, is expected to be conformant JSON. I currently have to adopt a string parser to read parts of the responses, to determine how to dispatch.
The semantics of the JSON is something we can discuss in a separate ticket. For example, a number of systems expect messages to be organized into "channels". We could do that in the payload, or we could later do that in the websocket URI. But that can be a different discussion.