Async client status?
asmakhalil opened this issue · comments
Hello!
I was implementing the coap RUST crate example: https://github.com/Covertness/coap-rs but then I learned that the client implementation is blocking. That lead me to this library, can anyone confirm that the coap-rs crate example is in fact blocking (at least the client bit) and if so would I be able to use this library to implement a non-blocking client? Or is it still a work in progress?
I also found this feature branch that modifies the coap-rs lib to have a non-blocking client: https://github.com/ryankurte/coap-rs/tree/feature/async-client, would I be able to just apply these changes and use the modified crate to achieve an async client?
Thank you!
Asma
howdy,
can anyone confirm that the coap-rs crate example is in fact blocking (at least the client bit) and if so would I be able to use this library to implement a non-blocking client?
when i last looked at it, coap-rs
only had a blocking client, hence the branch. i looked at extending this as you've discovered, but ended up implementing the basics here instead. it's likely there are things missing yet, but coap-client
provides an async coap client impl over tokio
that i have been using fine for some years.
would I be able to just apply these changes and use the modified crate to achieve an async client?
probably, i'm not sure what state that branch is in.
Hey!
Thanks for getting back to me!
Using coap-client
am I able to send different payloads set at command line? Or would I have to modify the lib itself to do that?
Thanks!
Asma