Support for concurrent send&recv

[obabec]

As of now client does not support concurrent send and pull action.
It would be more than pleasant to enable this feature so embedded devices with limited
socket capacity can do both actions.

[Nickztar]

Any updates on this?
Would love to get this in for my embedded device since i'm currently locked to only recieving atm.

Library is working great but this feature would really help, even if you could just point me in the right direction for implementing something like this.

[obabec]

Hello @Nickztar, my time is really tight these days as this is only my side project mainly developed as my thesis. I will try to take a look as soon as possible, but implementing this will take I think some time. But if you have sufficient memory you can still open 2 sockets (yes it is not ideal). Sorry for this, I would love to more work on this client but school and work together cuts my entire day away :(

[n8henrie]

But if you have sufficient memory you can still open 2 sockets (yes it is not ideal)

Do you mean to create 2 clients (one for publish, one for receive, each with its own socket)?

If so, won't most brokers refuse the second connection?

[gabevenberg]

@julian-graf In what way is this partially solved by #63 ? since poll isnt cancel-safe, is there some less-obvious way to do this?

[julian-graf]

You can achieve partial cancel-safety by calling Client::poll_header. This future can be cancelled anytime and you can send a message. Once you call poll_body though, you are stuck and have to wait until it completes unfortunately.