-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket support, live data subscriptions #151
Comments
Actually it seems that the bulk of the work is done in Orion: telefonicaid/fiware-orion#1669 |
Your right @cdupont, I didn't see the progress that they made. Is there any chance of enabling this feature with the Waziup broker? |
There is already the HEAD of Orion in Waziup... Maybe the feature is already present? Could you check? |
It is in a different branch: https://github.com/telefonicaid/fiware-orion/tree/feature/1181_websockets |
So we're back where the question began: Interested in a WebSocket gateway? |
It is a good idea to integrate the WebScoket in WAZIUP platform |
Orion dev replied: telefonicaid/fiware-orion#1181 (comment) |
closing as too old. Let's reopen another issue if still needed. |
For now, subscriptions to the fiware-orion broker will trigger an http request to a given endpoint.
This method is not usable for wep app clients, that can not function as an http server.
See telefonicaid/fiware-orion#1181
It seems like WebSocket has not been implemented yet.
As a solution to this, a WebSocket gateway can functions as a bridge between the clients and the broker.
WebSocket gateway
The gateway should connect
In order to listen for data changes, the client can open a websocket connection to the ws-gateway.
The gateway makes a subscription to the broker, and will pass any data-changes to the client via ws.
Closing the websocket connection will make the broker unsubscribe the previously create subscriptions.
Web Client <===WebSocket===> WS-Gateway <---HTTP---> Broker
What is your opinion?
I think, a Waziup WS-Gateway can boost the WebApps enormously.
The text was updated successfully, but these errors were encountered: