Since I have to bring my own I/O, do you have a reference implementation or 'glue' code examples for tokio, Bevy ,std::net so I don't have to write the event loop from scratch?
How does this integrate with the existing webrtc-rs media crates? Can I still use the media crate for packetizing H.264/Opus, or do I need to handle payload processing manually too?
encryption (DTLS/SRTP) layer interface with the Sans-I/O model? Does it rely on ring or openssl does that introduce blocking or heap allocations?
benchmarks comparing CPU usage between the async webrtc crate and rtc under high load?
Is API stable or should I expect breaking changes to the poll_ or handle_ methods in the near future?
are theer plan to support web transport, or is the focus strictly on webrtc 1.0?
since the library doesn't control the socket directly, how does it accurately estimate bandwidth to tell the video encoder to scale down?
sansio::Protocol API is stable, since crate sansio is stable v1.0.
The mdns-query-and-gather example shows how to control multiple I/O sockets to use and how to multiplex them with sansio::Protocol API.
For bandwidth estimation, you can register your own Interceptor with callback or event message to tell the video encoder.