[Q] Characteristics of different Inter Process Communication mechanism on Mac?
[Q] Characteristics of different Inter Process Communication mechanism on Mac?
- Subject: [Q] Characteristics of different Inter Process Communication mechanism on Mac?
- From: JongAm Park <email@hidden>
- Date: Thu, 06 Sep 2007 21:54:55 -0700
Hello.
I became curious about IPC mechanisms on the Mac platform.
Well.. there are at least 4 different type of IPC mechanism as far as I
know.
1. AppleEvent
2. NSDistributedNotification
3. Remote Messaging
4. Conventional IPC mechanisms based on socket/pipe/shared memory
I guess the method 4 is the basis of others.
Although Apple pushes the AppleEvent for scriptable application, you can
also use the mechanism for a simple IPC purpose, right? As far as I
know, the AppleEvent was introduced as an IPC mechanism for the System 7.
NS(Distributed)Notification mechanism seems to be widely used for
Cocoa/Objective-C programmers nowadays. Like the AppleEvent, I guess it
is processed through a central queue.
Probably there are pros and cons because of the fact.
Remote messaging enables IPC based on objects. So, you can use remote
objects like the way they are a local object. This mechanism seems to
offer simple way of inter-process communication by hiding underlying
mechanism like the one described as 4.
However, are there any special use cases where one method is preferred
to others?
Oh.. yeah.. for more subtle control of your own code, remote messaging
can be the best choice.
I welcome any answer or discussion. I guess this is very interesting topic.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden