I'm trying to better handle the case in which the device I'm talking to wanders out of range. Currently, calls to write return immediately and appear to queue up in some buffer - when the device comes back, it receives these messages*.
I'd like to be able to know that it hasn't received the messages after some timeout so I can report the device as missing.
I'm on Windows 7 64 bit using the Microsoft stack. I am wrapping a BinaryReader and a BinaryWriter around the NetworkStream returned by BluetoothClient.GetStream. I have tried setting a writeTimeout, without success.
* Usually this is only one or two because I'll block while trying to read the response.