Re: Seeking WebSocket proposal team

Hi Matthias

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

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

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).

The described message format was sufficient to meet the requirements.

TLTR;
If one strips down syntactic diffference, all of the mentioned protocols
encode command type in some way (POST/GET/PUT/...), command name - resource
and command data. Plus of course technical metadata.


Regards
Robert

On Mon, Oct 24, 2016 at 3:01 PM, Kovatsch, Matthias <
matthias.kovatsch@siemens.com> wrote:

> Hi Robert
>
>
>
> Thanks. Do you have a reference where this “COMMAND-MESSAGE” snippet
> comes from?
>
>
>
> Ciao,
>
> Matthias
>
>
>
> *Von:* Robert Gallas [mailto:gallas.robert@gmail.com]
> *Gesendet:* Montag, 24. Oktober 2016 13:48
> *An:* Dave Raggett
> *Cc:* Kovatsch, Matthias (CT RDA NEC EMB-DE); MEDINI LIONEL; bergi;
> public-wot-ig
> *Betreff:* Re: Seeking WebSocket proposal team
>
>
>
> Hi Matthias
>
> "How do people communicate over WebSockets?"
>
>
>
>
>
> Using WS as bidirectional communication IO channel only, to send command
> messages. JSON or Protocol Buffers.
>
> COMMAND-MESSAGE:
>   AUTH-DATA:
>   MSG-ID:
>   CORRELATION-ID:
>   COMMAND-TYPE: (GET/SET/ADD/REMOVE/CALL/REPLY/SUBSCRIBE/NOTIFICATION/
> ERROR)
>   COMMAND-NAME: (PATH-IN-DATA-TREE)
>   COMMAND-DATA:
>
>
>
>
>
> GET/SET/ADD/REMOVE sematics corresponds to manipulation data within
> hierachical data tree. CALL/REPLY is RPC style messaging.
> SUBSCRIBE/NOTIFICATION is obvious.
>
>
>
> Regards
>
> Robert
>