From: "J." <mailing-lists@xs4all.nl>
To: linux-c-programming@vger.kernel.org
Subject: optimal exchange of data inbetween 2 processes
Date: Mon, 10 May 2004 04:52:41 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0405100438130.16456-100000@hestia> (raw)
In-Reply-To: <409DAB41.1000608@sancharnet.in>
Monday, May 10 04:38:13
Hello,
I have almost fininshed the code for a program which is split in to two
processes. The only thing I have to do now is to connect them so that they
can exchange data.
One process generates data, the other one reads it. The amount of data
which needs to be transfered is fairly small, roughly 800 bytes a second.
What is the best way to implement this, with sockets or with pipes ?
Are there any 'general' guidelines for what option to use and what not to
use regarding the amount of data that needs to be transfered ?
Thnkx a lot.. If you guys could give me some thoughts..
J.
next prev parent reply other threads:[~2004-05-10 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 3:53 Serial revisited joy
2004-05-10 2:52 ` J. [this message]
2004-05-10 15:21 ` joy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0405100438130.16456-100000@hestia \
--to=mailing-lists@xs4all.nl \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).