Multiple things per WebSocket #46

Activity

1. benfrancis

   changed the title [-]Define websocket gateway API[/-] [+]Multiple things per WebSocket[/+] on Apr 3, 2018
2. benfrancis commented on Apr 3, 2018

   

   benfrancis

   on Apr 3, 2018

   Member

   More actions

   I agree it should be possible to have multiple things per WebSocket, as you say we just need to provide a thing ID (URI) in each message to indicate which thing it refers to.
3. YonasJ commented on Mar 4, 2019

   

   YonasJ

   on Mar 4, 2019

   More actions

   I would like to bump this idea.

   When implementing the API using the arduino API's for the ESP32 I have encountered some challenges:

   • The API's don't really support handling the websockets dynamically. So, it is a fair bit of extra coding to create an end point for each URL.
   • Each websocket uses a fair amount of the precious memory available.
   • I had to do a lot of duplication to support the HTTP and WebSocket API.

   I will put some comments in "Implement a single Websocket endpoint for things #947" as well.
4. benfrancis commented on Mar 6, 2019

   

   benfrancis

   on Mar 6, 2019

   Member

   More actions

   Proposal: Add an id field to WebSocket messages whose value is a URI identifying the thing the message relates to.

   {
     "id": "http://mythingserver.com/things/robot1"
     "messageType": "setProperty",
     "data": {
       "leftMotor": 100
     }
   }
   

   We also need to figure out how to expose the WebSocket endpoint as currently we do this in the links member of a Thing resource which corresponds to a single Thing.

   Perhaps if there is a Gateway capability the Thing Description for the gateway itself can have a top level links member which can link to a WebSocket endpoint for the whole gateway.
5. benfrancis commented on Mar 6, 2019

   

   benfrancis

   on Mar 6, 2019

   Member

   More actions

   Note that the W3C spec already has an id member for a Thing which is a URI identifying the Thing. This can optionally be the URL of the Thing Description.

   See also: #29

   👍React with 👍1Reacted by Philippe Coval
6. hobinjk commented on Jul 30, 2019

   

   hobinjk

   on Jul 30, 2019

   More actions

   As per the meeting today, this should come with a section or equivalent note that opening a websocket on /things will make a websocket corresponding to multiple things.

   This could be considered part of a Gateway capability
7. hobinjk

   added a commit that references this issue on Aug 22, 2019

   Describe Gateway /things websocket endpoint

   ...

   This issue will close once commit 8464dae is merged into the 'gh-pages' branch.

   8464dae
8. mrstegeman

   assigned

   hobinjk

   on Aug 22, 2019
9. mrstegeman

   unassigned

   hobinjk

   on Feb 21, 2020