Payload based protocols

w3c / wot-binding-templates

Web of Things (WoT) Binding Templates

http://w3c.github.io/wot-binding-templates/

Other

22 stars 25 forks source link

Payload based protocols #125

Open tuve opened 2 years ago

tuve commented 2 years ago

Is there anyway of describing an application protocol implemented as a json object over a common transport protocol such as websockets. One example of such protocol would be the eclipse ditto protocol over websockets. This is one example but we have several use cases that basically follows this pattern with a defined envelope format and a "value" or "payload" attribute as described by the data-scheme in the td.

https://www.eclipse.org/ditto/httpapi-protocol-bindings-websocket.html

relu91 commented 2 years ago

I think the best way is to use the subprotocol field. Just use it, if the protocol you are using does not define its own URI scheme. We have to start defining those subprotocols and collect them in this repo.

egekorkan commented 2 years ago

Call of 20.04:

We do realize that there are many cases where this happens, JSON-RPC is a popular example for example.
Sometimes there is a behavior behind the required payloads and putting this in data schema is not sufficient. A state machine would be needed inside (or linked to) TDs
Putting these in subprotocols is fine for now but if a Consumer implementation needs to handle 10+ subprotocols just because it is easier to package it like that, it would not be scalable.
We need a deeper thought process how to handle this in TDs. Postponing for 2.0

danielpeintner commented 6 months ago

@tuve you describe that you have "several use cases". Maybe you can expand on it a bit more since we are looking into new use-cases.

The option to use subprotocol might not be feasible in all cases.