Skip to content

Update API spec about Mqtt usage#114

Open
GwendalRaoul wants to merge 2 commits intomasterfrom
update-api-spec
Open

Update API spec about Mqtt usage#114
GwendalRaoul wants to merge 2 commits intomasterfrom
update-api-spec

Conversation

@GwendalRaoul
Copy link
Contributor

Update note for broker that are not 100% mqtt compliant
For qos=2 and retain flag mainly

Update note for broker that are not 100% mqtt compliant
For qos=2 and retain flag
of the gateway can be implemented instead of only once with the retained flag.
Consequently, backends will have to wait for a period time after the subscribing to
this topic before being noticed of all gateway status.
A period of 30s is a good tradeoff between loading the broker and reactivity for backends.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

30 seconds period might be too dense if backend needs to handle thousands of gateways. Maybe 30s - 5min would be better range. This should be configurable value.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can we have it as:

  • backends will pull it when needed
  • GW will publish it on change

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would change the API, not just the implementation

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

Successfully merging this pull request may close these issues.

3 participants