Re: CFSocket Read Call Back
Re: CFSocket Read Call Back
- Subject: Re: CFSocket Read Call Back
- From: "Duane Murphy" <email@hidden>
- Date: Thu, 29 Jun 2006 17:14:25 -0700
--- At Thu, 29 Jun 2006 16:52:50 -0700, Douglas Davidson wrote:
>
>On Jun 29, 2006, at 4:48 PM, Duane Murphy wrote:
>
>Is it normal for a read call back on a socket to be called when there is
>no data to be read?
>
>I create CFSocket from a socket and specify a read call back. The socket
>transfers some data, but then when there is no data available, the read
>call back is still being called.
>
>I am repeatedly call read on the socket, but it always returns 0 bytes.
>
>Is this normal behavior? I believe in some previous situation that the
>read call back would only be called when there was actually data available.
>
>
>CFSocket provides a read call back when select() indicates that the
>socket is readable.
>
Help me to understand what that means in real life. I am using a raw
ethernet socket.
What does it mean for a raw ethernet socket to be readable? read
obviously works even if there is no data available.
Thank you for your helpful insight,
...Duane
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden