site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Thread-index: AccUKc0QC9Dh/4AdEduB6wAX8i08Wg== Thread-topic: Kernel log: app uses send/recv on a pipe User-agent: Microsoft-Entourage/11.2.5.060620 Thanks a bunch for this tip! Ironically, this was my original implementation but then I thought that the kCFSocketDataCallBack is more elegant because I get a ready CFDataRef while kCFSocketReadCallBack required reading unknown amount of data (and I was afraid that I may block in read call if no data available). I did not notice that the kernel warning happened only after I switched to CFDataRef. This solves my problem. On a related note I wish it was possible to to create CFReadStream directly from file descriptor or FILE * stream (Cocoa NSFileHandle can initWithFileDescriptor) Thanks, Tom On 11/29/06 2:31 PM, "Quinn" <eskimo1@apple.com> wrote:
At 10:39 -0800 29/11/06, Vincent Lubet wrote:
The alternative is to use socketpair(2)
Or tell CFSocket /not/ to read the data for you (use kCFSocketReadCallBack instead of kCFSocketDataCallBack), in which case it will only notify you when data is available and leave you to read the actual data. Your callback can then read the data using <x-man-page://2/read> and avoid the message.
S+E
_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com