Re: CFWriteStreamCallback stops being called
Re: CFWriteStreamCallback stops being called
- Subject: Re: CFWriteStreamCallback stops being called
- From: Liwei <email@hidden>
- Date: Wed, 30 Jul 2008 23:35:14 +0800
Hmm, so I'll need to move some stuff to make a writer function. Thank
you for the idea!
Apple System Log, thanks!
2008/7/30 Shawn Erickson <email@hidden>:
> On Wed, Jul 30, 2008 at 8:02 AM, Liwei <email@hidden> wrote:
>> *Groans*
>>
>> How then do I check if the flag is set without polling? I thought the
>> whole purpose of using run-loops is to be able to eliminate the need
>> to poll something?
>
> Not sure why you think you need to poll? Also why would a runloop fire
> the same event every time it runs a cycle... then it would just be
> polling which it not what it is for.
>
> If your socket can accept more data then signal your writer to write
> data. If your writer doesn't have data to send then it does nothing.
> As soon as your writer has data to send (presuming it would know when
> this happened) it can explicitly check if the stream is ready to
> receive more data.
>
>> (A side question, is there something in OSX that I can use to log my
>> error messages? Something more native to OSX than stderr?)
>
> man asl
>
> -Shawn
>
_______________________________________________
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