Jens,
>> 2. However, CFReadStreams created _while_ the app was in the background
>> often (though not always) _don't_ call their callbacks _until_ the app is
>> brought in the foreground, then all of a sudden the callback happens.
>
> I think foreground/background is a red herring — that has a
Jens,
>> 2. However, CFReadStreams created _while_ the app was in the background
>> often (though not always) _don't_ call their callbacks _until_ the app is
>> brought in the foreground, then all of a sudden the callback happens.
>
> I think foreground/background is a red herring — that has a
On Jun 22, 2010, at 5:21 PM, John Michael Zorko wrote:
> 2. However, CFReadStreams created _while_ the app was in the background often
> (though not always) _don't_ call their callbacks _until_ the app is brought
> in the foreground, then all of a sudden the callback happens.
I think foregroun
Hello, all ...
I've an app that reads from the network using CFReadStream (it needs to use
CFReadStream so that it can throttle the connection and specify how many bytes
to read each time). What i'm finding is that CFReadStream callbacks aren't
always called when the app is in the background.
