Re: use of c select() style events with the objc run loop
Re: use of c select() style events with the objc run loop
- Subject: Re: use of c select() style events with the objc run loop
- From: j o a r <email@hidden>
- Date: Mon, 10 May 2004 19:55:55 +0200
What if you instead read the docs for NS/CFInput/OutputStream - do you
still feel the same way? If you're really afraid of blocking the main
thread, you can always spawn secondary threads.
j o a r
On 2004-05-10, at 19.38, Nicko van Someren wrote:
>
Yes, I read your posting and then went to look more closely at
>
NSFileHandle. Unfortunately my day job does not involve Macs so I
>
don't really have the luxury of time to read every bit of
>
documentation end to end.
>
>
That said, as far as I can tell the the NSFileHandle object and it's
>
notifications do not actually do all of what Robert wanted, since he
>
needs to "transmit typed content from an NSTextView without the serial
>
port routines blocking" and the writeDate: message is synchronous and
>
may still block. To do this we still either need to call select()
>
with a write flag or catch the appropriate kernel event on that file
>
descriptor.
>
>
I've still not found a generic way to bridge kernel events into the
>
run loop, only function specific ones like the file handle
>
notifications.
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.