Re: Best way to implement performant Interprocess Communication
Re: Best way to implement performant Interprocess Communication
- Subject: Re: Best way to implement performant Interprocess Communication
- From: Aurélien Hugelé <email@hidden>
- Date: Sat, 17 Dec 2005 07:03:47 +0100
I really depends of your needs :
do you need communication between several processes on several hosts
or just on one host ?
- Cocoa's DO are *very* light and efficient when using NSMachPort,
but only work on the very same host (no network communication
possible here).
- Cocoa's DO using NSSocketPort are quite light and efficient and
works across networks, but they are not compatible with other well
known platforms since they do not implement cocoa's DO.
- (Good Old) Socket communication is harder to implement that the
both above, you can't get the coolness of cocoa's DO (you will not be
able to make NSObjects communicate with message, keep the clean cocoa
syntax, you'll have to do the serializing stuff your self to exchange
datas etc...) but you can get something cross-platform compatible.
Note that switching from NSMachPort to NSSocketPort using cocoa's DO
is very easy and quick, so you might want to begin with mach ports,
then, if really necessary, switch to NSSocketPort to achieve the same
result across network! i think it is a killer !
On 17 déc. 05, at 01:57, Ralf Hasemann wrote:
Hi Cocoa people!
I am exploring the different opportunities for interprocess
communication
in OS X and I have written small examples for:
- Socket communication
- Distributed Notifications
- Distributed Objects
Since it is not guaranteed that Distributed Notifications are
delivered at all,
this kind of communication does not fit my needs.
What I wonder now is which of the remaining two (Sockets & Dist.
Objects)
is the most performant way (regarding throughput and less overhead) to
implement interprocess communication??
I read some notes about Mach Messaging, but my understanding about
it is, that it is the foundation of the Distributed Objects
mechanism - am I correct
in my assumption?
Is there any other way to implement performant Interprocess
Communication?
Thank you very much for any help!
Best regards,
Ralf Hasemann
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gumitech.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden