Re: The joy of pipes

On 11/18/24 4:20 AM, Pancho wrote:

On 11/18/24 06:51, 186282@ud0s4.net wrote:

On 11/18/24 1:06 AM, Lawrence D'Oliveiro wrote:

On Sun, 17 Nov 2024 22:50:41 -0500, 186282@ud0s4.net wrote:
>

As I said somewhere, if your child processes are sending megabytes
back to the parent you're DOING SOMETHING WRONG.

>
Says the one who has no clue how to write real-world programs.

>
   Am I supposed to say something horrible about
   you now ?
>
   Nope. Won't. I'm sick of 'The Wars'.
>
   Clue - I've writ 'real world programs' and
   got paid well for them from the punch-card
   days on. I did it my way, for my reasons,
   my 'vision'.
>
   And so did you.

 I mainly did as I was told. In large political organisations following your own vision can be problematic. You have to fight for a vision.

   I very intentionally stayed away from such orgs. A little
   less money, but the happiness factor more than compensated.
   Got to pursue many esoteric projects - some of which WERE
   useful - and the org paid for most of it (except the odd
   Radio Shack parts).

I've no idea why using IPC to send megabytes of data between different processes is wrong. That is what many service-orientated architectures do. The moment you have a persistence service it is likely to happen.

   Really you DON'T want to send megabytes as IPC ... but
   somebody somewhere MAY wanna. So, what's the best way
   for them to do that ? Don't necessarily piss on 'em but
   help 'em out instead.

Although to be fair we very rarely used pipes, directly, almost never. It was always something like REST or message queues.

   Again though, just "blocks of information". MANY ways
   to do that. Each developer has to figure out what's
   best for THEIR particular app.
   I mentioned a server style app I made, but I wanted the
   child processes/threads (tried both ways) to return
   some active stat data to the parent. Not a huge amount
   of info, but useful. Pipes were the best way. The
   parent was allowed to xmit a 'kill' to a child in
   trouble, via the pipe, so it could shut down in an
   orderly fashion.
   Pre-threaded servers seem to have the highest capacity
   and throughput. The parent allocates maybe ten threads
   to start off with and then can add new blocks of ten
   as-needed. It's a little harder to manage than some
   other kinds of servers, and sometimes a bit harder
   to visualize how it's working, but they're good things.
   Once you've got it you're SET.