Re: Timeouts on CFWriteStreams
Re: Timeouts on CFWriteStreams
- Subject: Re: Timeouts on CFWriteStreams
- From: Ulrich Bauer <email@hidden>
- Date: Tue, 4 Mar 2003 17:34:11 +0100
On Tuesday, Mar 4, 2003, at 00:19 Europe/Berlin, Jeremy Wyld wrote:
CFStream does no buffering, so it'll be the kernel's socket buffer.
Is this still a great problem? At some point, you will timeout
waiting to fill the buffer again (it's full) or waiting to hear back
from the server. Either way, the timer should fire for you.
If you're using a CFSocketStream, you should receive a read event at
some point. When you attempt to read, you should get a zero.
Unfortunately, this is all a little bit too unreliable for me. Since I
don't send great amount of data and have no keepalive or ack signal, it
takes too much time until I realize that the remote side has died; I
can still put quite a lot of data into the buffer until it is full.
Why do I get the kCFStreamEventCanAcceptBytes event at all, even though
no data could be written to the socket since the last time I called
CFWriteStreamWrite()? And why is the CFWriteStream in status
kCFStreamStatusOpen and not in status kCFStreamStatusWriting when I
receive kCFStreamEventCanAcceptBytes and the buffer is not yet empty?
Cheers,
--
Ulrich Bauer Mail: email@hidden
Lehrstuhl f|r Angewandte Softwaretechnik Tel.: +49 (89) 289-18240
Institut f|r Informatik Raum: 01.07.039
Technische Universitdt M|nchen PGP ID: 0361C54B
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.