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

Failure to attain QoS is not bad #1845

Merged
merged 1 commit into from
Aug 1, 2019
Merged

Failure to attain QoS is not bad #1845

merged 1 commit into from
Aug 1, 2019

Commits on Jul 28, 2019

  1. Failure to attain QoS is not bad

    Prior to this commit, a failure to attain a QoS level i.e. subscribe, was considered bad. The spec treats this condition as one being something for the application to handle e.g. a client can decide to proceed or not given that one of the topics being subscribed was able to be so.
    
    The fix is to deprecate the BadSubAckMessage and always return SubAck. This then permits the Subscriber to process SubAcks whether they are good or bad from the application's perspective.
    huntc committed Jul 28, 2019
    Configuration menu
    Copy the full SHA
    c2bf13b View commit details
    Browse the repository at this point in the history