site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com At 21:19 -0500 on 1/8/07, Greg wrote: This looks very interesting and so far it seems to be exactly what I want as it uses a familiar API (bsd sockets) and allows for bidirectional communication. With this available I don't see why anyone would want to use sysctl or the IOUserClient stuff... are there any disadvantages associated with using kernel control sockets over the aforementioned sysctl/IOConnectMethod stuff? It all depends on what your trying to do... IOUserClient is quite fast (possibly faster than sockets, and definately not slower). It also makes it possible to create true "API's" in a way that sockets don't readily support (See the SCSITaskUserClient, FireWireUserClient, etc...). It really isn't that difficult to use and is well documented. I don't have time to search right now, but their are at least 2 UserClient samples on developer.apple.com. It might be over kill for what your doing, but it all depends... You haven't mentioned a lot of detail about what your doing (how fast the data needs to be moved, how often, etc.), but setProperty is also an option for passing data into the kernel. It's by far the easiest to implement and if you don't need high performance and you aren't moving lots of data it's a reasonable option. -- ______________________________________________________ Arguing with an engineer is like wrestling with a pig in mud. After a while, you realize the pig is enjoying it. ______________________________________________________ Kevin Elliott <mailto:kelliott@mac.com> AIM/iChatAV: kelliott@mac.com (video chat available) ______________________________________________________ _______________________________________________ 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