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

Non-blocking solution? #36

Closed
Ryanauger95 opened this issue Sep 6, 2017 · 1 comment
Closed

Non-blocking solution? #36

Ryanauger95 opened this issue Sep 6, 2017 · 1 comment

Comments

@Ryanauger95
Copy link

Is there any plan to support a non-blocking api in the future? For most applications, it is important to be able to publish and subscribe at the same time.

@dgarske
Copy link
Contributor

dgarske commented Sep 7, 2017

Hi PiedPieper,

We do support non-blocking mode using ./configure --enable-nonblock or #define WOLFMQTT_NONBLOCK. This prevents any call from blocking and will return with MQTT_CODE_CONTINUE. This mode only works correctly in a single thread or if you manage the context between two threads yourself. With non-blocking mode you could accomplish your requirement.

I believe the feature you are requesting is multiple-thread support, which is at the top of our feature list to add.

Thanks,
David Garske, wolfSSL

@dgarske dgarske closed this as completed Oct 9, 2017
kojo1 pushed a commit to kojo1/wolfMQTT that referenced this issue Aug 21, 2022
Link sha256.o module even if sha3 is selected, as it's needed by RSA
This issue was closed.
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

No branches or pull requests

2 participants