• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Best way to implement performant Interprocess Communication
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best way to implement performant Interprocess Communication


  • Subject: Re: Best way to implement performant Interprocess Communication
  • From: Markus Hitter <email@hidden>
  • Date: Sat, 17 Dec 2005 13:13:41 +0100


Am 17.12.2005 um 01:57 schrieb Ralf Hasemann:

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??

Depends on what you want to "communicate" about. If you primarily want to send messages, DO should be the right thing. If you want to push over a huge amount of data, sockets most likely perform better.


Is there any other way to implement performant Interprocess Communication?

- Shared memory (it seems to have less functionality than on Linux, though).

- "Communication" via shell scripts generated as needed.

- Pipes/named Pipes. Similar to sockets, faster, but local only.


HTH,
Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/




_______________________________________________
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
  • Follow-Ups:
    • Re: Best way to implement performant Interprocess Communication
      • From: "Sean McBride" <email@hidden>
References: 
 >Best way to implement performant Interprocess Communication (From: Ralf Hasemann <email@hidden>)

  • Prev by Date: Re: Using Zip executable in Cocoa Application
  • Next by Date: Re: send an Action without a button
  • Previous by thread: Re: Best way to implement performant Interprocess Communication
  • Next by thread: Re: Best way to implement performant Interprocess Communication
  • Index(es):
    • Date
    • Thread