Talk:Inter-process communication

From Wikipedia, the free encyclopedia

Hmm, the article is very Unix-minded, I've just included link inmailbox article to here but it is not mentioned here, in vulgar terms the mailbox is a object of messaging mechanism. You create can create a mailbox and receive the messages from any processes, knowing its ID or in other cases have a pointer to it's contorol block, also when you try to receive a message you pass execution to other tasks. This kind of communication does not fit anywhere in any method described in here. While its implemented in uC/OS RTOS and Windows(message queue fits, but it's process-global). Gnomz007 01:39, 23 May 2005 (UTC)

Why SOAP is in the list of 'platform specific APIs'?! Samokhvalov 11:21, 04 Mar 2006 (GMT)

I've moved SOAP and XML-RPC to the 'platform-independent' list, along with Internet Communications Engine. Perhaps more controversially, I've also put that list into chronological order. Cheers, CWC(talk) 14:44, 23 August 2006 (UTC)

[edit] Inter-process or intra-process

The introduction states that IPC is "a set of techniques for the exchange of data between two or more threads in one or more processes" - this makes no sense to me. If it is inter-process then it should be "two or more processes" and not "two or more threads". As far as I know, *nix OS create a new process when you fork() - not just a new thread. In general, if I have two threads that are truly within one process I don't need inter-process communication. Manassehkatz 03:38, 4 December 2006 (UTC)

It certainly makes sense... you just have to have a vague definition of "process". After all, there are different types of threads (soft/hard) as well.

What bugs me is this article makes no mention of signals. Signals are certainly a form of communication between processes. I was wondering what communication methods might be related to Ctrl-C in windows (windows doesn't have signals as far as I know, but they ought to have "something"). If parent X tells child process Y to die, how is that work? Is it in effect asking the OS to kill Y? Root⁴(one) 16:05, 3 May 2007 (UTC)

I take that back. The heaviest threads, called Light weight processes (see Threads (computer science)), may not strictly need IPC. They will require semaphores or some other locking mechanisms, though. Root⁴(one) 16:14, 3 May 2007 (UTC)

booo —Preceding unsigned comment added by 217.41.122.130 (talk) 15:02, 21 September 2007 (UTC)

[edit] German version

The German version of this article seems much more well-written. How about replacing the English page with a translation of the German? 194.237.142.21 12:22, 20 June 2007 (UTC)

Is there any way we can do it without obliterating too much of the content? I kinda like having a list of IPC APIs and methods. Root⁴(one) 19:10, 20 June 2007 (UTC)

jaa