Skip to content
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

Multiple property updates in a single message #109

Open
benfrancis opened this issue Oct 3, 2018 · 5 comments
Open

Multiple property updates in a single message #109

benfrancis opened this issue Oct 3, 2018 · 5 comments

Comments

@benfrancis
Copy link
Member

As a developer I would like to stream property updates with multiple updates batched per message so I don't have to send a separate message for every change

Suggested by @draggett, particularly for industrial use cases.

@benfrancis
Copy link
Member Author

My first question would be whether the overhead of a WebSocket message is big enough to mean that sending a message per update is not practical?

@draggett
Copy link

draggett commented Oct 3, 2018

We should try some experiments to measure the impact. These could look at batching vs individual events, and the effects of compresssion algorithms. We should cover examples where each update includes data from multiple sensors, as is common for telemetry use cases.

@mrstegeman
Copy link
Contributor

This is actually being done already in our webthing-arduino library.

@benfrancis
Copy link
Member Author

@mrstegeman wrote:

This is actually being done already in our webthing-arduino library.

Is that updating multiple properties in a single message (which the specification already describes), or sending multiple updates of the same property in a single message (which is what I think this issue is about)?

@mrstegeman
Copy link
Contributor

It's sending multiple property statuses in a single propertyStatus message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants