You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subscriptions may be created to properties and actions by a GET request on a property or action resource which is upgraded to a WebSocket connection such that data can be pushed from the server to the client when necessary.
There may be use cases where a client wants to subscribe to events other than changes in property resources or the creation of or changes to action resources.
For example, a Thing may have a "temperature" property which could be subscribed to whenever the temperature changes, but the Thing may also want to emit an event only when the temperature passes a certain threshold.
Should we add an "events" member to the Web Thing Description in addition to "properties" and "actions" for this type of use case? Is there a way for events be represented by resources in a RESTful way?
The text was updated successfully, but these errors were encountered:
Subscriptions may be created to properties and actions by a GET request on a property or action resource which is upgraded to a WebSocket connection such that data can be pushed from the server to the client when necessary.
There may be use cases where a client wants to subscribe to events other than changes in property resources or the creation of or changes to action resources.
For example, a Thing may have a "temperature" property which could be subscribed to whenever the temperature changes, but the Thing may also want to emit an event only when the temperature passes a certain threshold.
Should we add an "events" member to the Web Thing Description in addition to "properties" and "actions" for this type of use case? Is there a way for events be represented by resources in a RESTful way?
The text was updated successfully, but these errors were encountered: