Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

umqtt.{robust,simple}: wait_msg(): select blocking mode by parameter #196

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

Open
puuu wants to merge 2 commits into micropython:master
base: master
Choose a base branch
Loading
from puuu:umqtt.robust.check_msg3

Conversation

@puuu
Copy link
Contributor

@puuu puuu commented Jul 10, 2017

As described in #192 , check_msg() block after reconnect. Saving the blocking state in a parameter allows to reapply the blocking mode to the socket.

This PR did not address the issue that check_msg() blocks until reconnected.

straga reacted with thumbs up emoji
puuu added 2 commits July 10, 2017 12:32
Knowing the blocking state in wait_msg() allows easier overwriting of
the wait_msg() method in subclasses like umqtt.robust. Since the
blocking mode of the socket can not be read, a additional parameter is
used.
Since, after reconnect the blocking mode of the socket is lost,
check_msg() will block like wait_msg(). Holding it a separate
parameter allows to reapply the wanted blocking mode later on.
Please see also the related commit to umqtt.simple.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /