You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ironically, with the sparse state of COAP in Rust, it might be easier to implement an async version of COAP handlers.
However, I can imagine for consumers of the API, such as Element, matrix-rust-sdk, or other mobile clients, it might be easier to embed a synchronous API when interfacing with via FFI.
So the question becomes; how to implement that? How to expose interfaces? Should a whole sub-crate be dedicated to this, or should async APIs offer a sync version? How would this interact with mixed async/sync calls?
The text was updated successfully, but these errors were encountered:
I was mostly looking at coap, though i think that with coap-lite, a simple synchronous API is easier at this stage, and i'm then inclined to put async behind a crate feature flag.
Ironically, with the sparse state of COAP in Rust, it might be easier to implement an async version of COAP handlers.
However, I can imagine for consumers of the API, such as Element, matrix-rust-sdk, or other mobile clients, it might be easier to embed a synchronous API when interfacing with via FFI.
So the question becomes; how to implement that? How to expose interfaces? Should a whole sub-crate be dedicated to this, or should async APIs offer a sync version? How would this interact with mixed async/sync calls?
The text was updated successfully, but these errors were encountered: