Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: The joy of pipes
Date: Mon, 18 Nov 2024 09:36:16 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <vhf1qg$165g7$1@dont-email.me>
References: <vgns2aqlhq@dont-email.me> <20241112111426.00007245@gmail.com>
	<e44df1bda1f1622a8d725c69860d3225@msgid.frell.theremailer.net>
	<m2ttc9y3d8.queerchen@cmschueller.my-fqdn.de> <eli$2411141855@qaz.wtf>
	<20241114160907.0000252b@gmail.com> <vh6a9k$33c17$5@dont-email.me>
	<hzSdnTUBKbG_YKv6nZ2dnZfqnPQAAAAA@earthlink.com> <A7GZO.66$hgYd.23@fx41.iad>
	<wwvr07bpizm.fsf@LkoBDZeT.terraraq.uk>
	<JJOdnfSeXoej5aT6nZ2dnZfqnPSdnZ2d@earthlink.com>
	<wwvwmh2z1y3.fsf@LkoBDZeT.terraraq.uk>
	<Uv-dnfY4yvgPJKf6nZ2dnZfqnPSdnZ2d@earthlink.com>
	<vhelgl$142m9$2@dont-email.me>
	<UricnZ0glICSeaf6nZ2dnZfqn_adnZ2d@earthlink.com>
	<vhf0sn$15fdk$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 18 Nov 2024 10:36:17 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b3d2674dac7de3bb2b439499c252dd12";
	logging-data="1250823"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18HJMvaqarsNTaHUpkjA+wU"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:1E6cErO19H2u/MInvFj7KX1GfwU=
Bytes: 2502

On Mon, 18 Nov 2024 09:20:23 +0000, Pancho wrote:

> I've no idea why using IPC to send megabytes of data between different
> processes is wrong.

It is something I have done. It’s perfectly commonplace.

> Although to be fair we very rarely used pipes, directly, almost never.

I have used pipes, I have used Unix sockets, I have used network sockets.

If you are running a Linux GUI, then almost certainly it is built on D-Bus 
as a high-level IPC mechanism that is used as a core component. That is 
designed to run over Unix sockets. It is not itself designed for high-
bandwidth data transfers; if you want to do that, you can exchange your 
own D-Bus messages to set up custom pipe or Unix socket connections 
between bus peers.

> It was always something like REST or message queues.

Message queues are an OS-provided primitive, but REST is not -- that is a 
protocol, not a transport. What transport(s) did you use for that? I would 
assume network connections.