Websocket Support for Context Broker

[IAIS4EP]

Websocket Support for Context Broker:

In order to make the device and backend communication efficient it is desired by the Orion Context broker to support Websocket transport protocol.

[fgalan]

Related questions at SOF:

• http://stackoverflow.com/questions/32402035/fiware-orion-websocket-support
• http://stackoverflow.com/questions/29930412/orion-context-broker-context-subscriptions-with-android-client

[jmrobles]

+1 (and congrats, Orion is becoming a really important piece of IoT infrastructure)

[fgalan]

CC: @fortizc

We are going to start this work in November 2015 sprint. Let's see how it goes... :)

[jmrobles]

Olé!! 👍
Just in time! We need that feature in this moment.
Thanks!

[fgalan]

A first proof of concept will be done, based on the following encoding:

{
   "verb": "POST",
   "url": "/v2/entities",
   "headers": {
      "Fiware-Service": "myServ",
      "Fiware-ServicePath": "/test2",
      "X-Auth-Token": <...>
   },
   "payload": {
      "type": "Room",
      "id": "Bcn-Welt",
      "temperature": 21.7,
      "humidity": 60,
      "location": {
         "value": "41.3763726, 2.1864475",
         "type": "geo:point",
         "crs": "WGS84"
      }
    }
}

(Responses will be encoded in a similar way)

That way, it could be relatively easy to "link" the fields in the above JSON envelop with the current CB logic (ConnectionInfo mainly).

I would like to stress that this would be a first proof of concept. Once we achieve this step, evolutions and optimization of it would be done (anybody is welcome to suggest! please use the comments to this issue).

[fortizc]

Add a little example of libwebsockets a server and the client

[jbheren]

+1 This is woulde me a must, actually Orion's subscription needs an external url to receive messages

It would be a must Orion had a subscribe mechanism in the way Faye makes it : a client that has internet access subscribes to a channel on the server & stays connected using a socket.

Wish you the Best