Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sosend, soreceive, soconnect

On Jan 20, 2004, at 5:57 AM, Mike Smith wrote:
On Jan 19, 2004, at 9:29 PM, Justin Walker wrote:
On Monday, January 19, 2004, at 09:05 PM, Matt Jaffa wrote:
Please advise me in this area,
I am looking to finish my project quickly.

You will need to adjust your goals. It doesn't appear that you have much experience with this kind of development, and this is tricky code.

Amen. Tuning this will take some time, too.

Look at the Darwin sources ... <snip>.

Most everyone first choses a user<-->kernel communication mechanism based on the way data is supposed to be handled in the "typical" case. But the real trick is determining what you want the edge-case semantics to be. For instance, what happens when the daemon is not keeping up with the filter and more data keeps coming in? Do you drop the data? Do you queue it? For how long and how much? If data is dropped, how do you detect it and recover from it? The answers to these questions, matched against the behavioral characteristics of the user<-->kernel communications mechanism available to you, will go much further towards pointing out a selection than an arbitrary "it's networking code so it has to be a socket" kind of dogma (but obviously a socket tends to match the semantics _most_ networking code expects).

--Jim
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: sosend, soreceive, soconnect (From: Justin Walker <email@hidden>)
 >Re: sosend, soreceive, soconnect (From: Mike Smith <email@hidden>)



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.