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
The library supports the server side receive maximum, using a weighted semaphore to ensure that we do not have more inflight messages than the server allows, there is not yet any checking in the client to ensure that if a receive maximum was set by the client the server has not broken it. Although there is a field in the client called clientInflight declared as a weighted semaphore, this might not be the best method of tracking this (perhaps just an atomic counter?)
The text was updated successfully, but these errors were encountered:
alsm
changed the title
Support client side receive maximum
Client side receive maximum
Nov 2, 2018
http://docs.oasis-open.org/mqtt/mqtt/v5.0/cs02/mqtt-v5.0-cs02.html#_Toc514345321
The library supports the server side receive maximum, using a weighted semaphore to ensure that we do not have more inflight messages than the server allows, there is not yet any checking in the client to ensure that if a receive maximum was set by the client the server has not broken it. Although there is a field in the client called
clientInflight
declared as a weighted semaphore, this might not be the best method of tracking this (perhaps just an atomic counter?)The text was updated successfully, but these errors were encountered: