Re: -rfcommChannelData: behavior characteristics
Re: -rfcommChannelData: behavior characteristics
- Subject: Re: -rfcommChannelData: behavior characteristics
- From: Marco Pontil <email@hidden>
- Date: Tue, 3 Jan 2006 09:59:10 -0800
What happens if an application's main thread gets starved for any
length of time while there's lots of incoming data on an RFCOMM
channel?
The flow control should take care of this and realize that the
internal buffer is filling up and prevent the other side from sending
data (hopefully the other side will respect the flow control).
Will IOBluetooth grow its internal buffer to hold all the data and
hand all of it off to the delegate when the thread processes its
loop sources, or will I start to lose data?
No, but flow control should take care of it. If packets are lost (we
get it but there is no room to put them) an error is sent so at least
the sender knows that the data is lost, but it should not happen.
Marco
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden