futures-channel doesn't support blocking send, so in the callbacks from java
(which are not in an async context) we're forced to do try_send, which will lose
data if the channel is full because the Rust side is too busy.
This is not a big deal for scanning, but is for stuff like gatt/l2cap responses that
are coming next.
futures-channeldoesn't support blocking send, so in the callbacks from java (which are not in an async context) we're forced to dotry_send, which will lose data if the channel is full because the Rust side is too busy.This is not a big deal for scanning, but is for stuff like gatt/l2cap responses that are coming next.