AW: Seeking WebSocket proposal team

Hi Robert

Command message is one of the enterprise integration patterns. http://www.enterpriseintegrationpatterns.com/patterns/messaging/CommandMessage.html with free inner structure.

Okay, that part does not define much (basically that it is a message sent from A to B).

Described inner structure is inhouse solution designed based on experience with HTTP, REST, SOAP, XML-RPC, NETCONF.

Yes, so you defined a protocol that you needed, since WebSockets alone cannot provide for that.
Do you have experience with using this inhouse solution across multiple stakeholders, e.g., to integrate services of other companies?

Rationale behind the design was to abstract away transport protocol specific stuff and to create message format which could be reused by WS for example.

Requirement was to:
- manipulate data in a hierarchical datatree (like REST)
- call (invoke) actions in a simple way (like XML-RPC)
- pub/sub (like MQTT).

What would be your conclusion when comparing this with, for instance, CoAP-over-WebSockets (considering REST+Observe over a firewall-friendly transport)?

Thanks,
Matthias