FROM : ben syverson
DATE : Fri May 16 00:40:41 2008
On May 15, 2008, at 5:33 PM, Hamish Allan wrote:
> NSRunLoop is just Cocoa's implementation of a kevent()-style loop.
> Instead of adding your socket to the kqueue, add it to the run loop
> instead. (See e.g. http://cocoadevcentral.com/articles/000039.php --
> which uses the CFRunLoop interface, but it's the same run loop.) No
> need for a separate thread to handle the main task.
I know it's kevent "style," but unless it's actually kevent (or a
similar kernel-level event system) under there, I have my doubts about
the performance under heavy load. I guess I could (should) do
benchmarks of both versions. But kqueue is working great so far, so
I'll probably leave any benchmarking & Sharking until after the rest
of development is done...
Thanks to everyone for their help! It's been most... helpful. :)
- ben
DATE : Fri May 16 00:40:41 2008
On May 15, 2008, at 5:33 PM, Hamish Allan wrote:
> NSRunLoop is just Cocoa's implementation of a kevent()-style loop.
> Instead of adding your socket to the kqueue, add it to the run loop
> instead. (See e.g. http://cocoadevcentral.com/articles/000039.php --
> which uses the CFRunLoop interface, but it's the same run loop.) No
> need for a separate thread to handle the main task.
I know it's kevent "style," but unless it's actually kevent (or a
similar kernel-level event system) under there, I have my doubts about
the performance under heavy load. I guess I could (should) do
benchmarks of both versions. But kqueue is working great so far, so
I'll probably leave any benchmarking & Sharking until after the rest
of development is done...
Thanks to everyone for their help! It's been most... helpful. :)
- ben






Cocoa mail archive

