| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Monday, July 30, 2001, at 03:47 PM, Andreas Monitzer wrote:[...]
However, when this code is run the notifications are constantly sent ("Notification without data!") and the CPU utilization is at about 25% even when nothing happens. "waitForData" doesn't sound like it should send notifications when no data is available. Can anyone confirm/deny/explain this?
I think I'll implement it myself by using select().
Why not have the file handle do the reading for you with -readInBackgroundAndNotify? I'm not sure waitForDataInBackgroundAndNotify (which uses select()) works well (gives the semantics you're expecting) on real files (as opposed to pipes or sockets).
The no-data could be because there is an error occurring (say, in the background wait) or because no data has been added to the file (your fd is still "at EOF") but select() is returning the file descriptor as readable anyway.
In any case, I'd try converting to -readInBackgroundAndNotify.
In a former life I reported an apparent bug in select() all the way back to NeXTSTEP 2.0
At the time it seemed that select always returned "ready" but had zero bytes
to be read. I seem to remember thinking that it was triggered by select calls against tty/pty file handles.
| References: | |
| >Re: NSFileHandle notifications (From: Chris Kane <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.