At 10:57 +0300 26/4/03, Oleksiy Gorelov wrote: Could some body explain, how two independent applications on the sam host can establish connectin for IPC. To get a meaningful answer you really need to give more details about your requirements. How much information do you need to pass between your client and server? The total size of data passed between the two and the expected number of requests per second is both important. Do you have lots of different types of client/server requests (and thus would like RPC parameter marshalling), or just a single one. What does the main event loop of your server look like? There are /many/ IPC mechanisms on Mac OS X, so choosing the right one requires some analysis. At second, I read kernel_principles and kernel_interfaces pdfs. And I dont understand how one task can send port right to other task if it does not have already send right for one port of the task? Does it mean that IPC can be established only between paren and child processes? For Mach IPC, the server typically registers with the bootstrap server and the client looks up the server via bootstrap server calls. See /usr/include/servers/bootstrap.h for details. At last, I can use POSIX sokets in AF_UNIX mode, but Is it efficiently implemented on OS X? Do you want to know whether it's efficiently implemented, or whether it's implemented efficiently enough for your needs? I'm presuming the latter, hence my first question. We can't tell you whether it'll meet your needs unless you tell us what they are. S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Technical Support * Networking, Communications, Hardware _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.