Re: [Tapioca-devel] Ideas on the plumbing protocol

[Richard F. <rj...@fi...>]

On Fri, 6 Jul 2001, Eric Lee Green wrote:

> 1. The actual low level network communication widget just
>  sends stdin/stdout across the network, encrypting it via a stream cipher
> (I suggest RC4, since OpenSSL does RC4 just fine).
>
> 2. At each end, there is a multiplexor for the multiple inputs
> (stdout, stderr, various named pipes), and a de-multiplexor that
> takes a stream coming from the other end and turns it back into the
> multiple streams, sending those streams wherever.

Sounds good.  Saves us from having to open a second socket for
stderr/control.  And since we are talking about some kind of protocol
between the MP and DMP, that can also incorporate a close command that
causes a particular channel to close.

> than writing from scratch. Sigh. Oh well, time to crack the Stroustrup.

Yes, Stroustrup (Special Edition) is now my bible.  I discovered that C++
has changed a bit in the last few years.  Either that, or my knowledge of
C++ wasn't quite correct to begin with!

For example, the C declaration "NULL" is now passe.  You initialize
pointers with "0", not NULL.  It's a hard habit for me to break.

Namespaces are also new, and something I haven't used.

-- 
Richard Fish, Unix/Linux Software Engineer, rj...@fi...