On 02/13/2014 03:26 PM, Stef Walter wrote:
So as we discussed elsewhere ... past proof-of-concept, our internal
protocol needs a bit better framing in order to handle the modularity
stuff and be extensible.
* Use only one Websocket for efficiency
* Connect out to multiple DBus services (not just cockpitd)
* Support multiple payload types in future (not only dbus-json)
* Alternate credentials (ie: initial setup)
Here's a first whack at documenting what it might look like:
The protocol looks usable, I would only add also 'protocol version'
field, this can save a lot of headache when you consider moving from
json to something else.
Out of curiosity, are there any alternative already defined/used protocols?