-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Add support for real-time communication #34
Comments
This is also related to #4: Once the interval can be defined per backend API, it can be decreased for specific data sources. However, it remains to see how the service will work if interval is only, say 1 second? |
I think it could be saner to let the backend stream its data to the component, perhaps introducing a subscription type |
Sounds good to me. Thanks. |
Any progress with this? |
any news ? |
@juhamust, @cybernet done! available in And of course, if you have any feedback/issue with it, just let me know! |
Current polling model work nicely most of the cases. However, if more accurate data is needed, the approach no longer. Thus, it should be possible for client to communicate with the client whenever needed.
Example scenario: Server side client creates a WebSocket or MQTT connection to data source. Whenever a message is received, client communicates it to all the interested widgets.
@plouc: I'm sure you have an idea how to implement this without affecting too much on the API.
The text was updated successfully, but these errors were encountered: