What is the architecture here? Peer-to-peer, client-server?

packets floating in a TCP/IP stream with a field in the binary format for "substream ID" or something like that would be doable.

That's all multiplexiing really is ... packets inside of some encapsulating format.

Pack/unpack is a PITA ... if someone has a good Perl-data-structure to binary implementation, I'd like to hear of it too, something like YAML (or even the dreaded XML) would be language agnostic, but you don't want to send that over the wire if you care about efficiency. Heck, you really don't want to parse it either. If it's Perl <-> Perl maybe Storable is okay, you could freeze a packet class or something?

In reply to Re^3: Multiplexing Stuff by SpanishInquisition
in thread Multiplexing Stuff by Eyck

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.