in reply to Re: Good IPC Message Protocols?
in thread Good IPC Message Protocols?

I think you missed the part where the keys and values are base64'd as part of the serialization. Which actually increases the things that can be transmitted easily, and improves robustness because the payload can't be confused with the framing.

So while I agree with the principle of not reinventing wheels, especially when security is on the line, pileofrogs isn't as misguided as all that.

Replies are listed 'Best First'.
Re^3: Good IPC Message Protocols?
by BrowserUk (Patriarch) on Jan 31, 2009 at 00:49 UTC

    Now you point it out, you're right++.

    I got hung up on the "64 characters" bit and completely forgot that the input to the encoding process can contain any byte values.

    That said, I still much prefer length prefixing (via pack 'n/a*' etc.) which also allows the data packet to contain all byte values, but has the added advantages of:

    • 4(or 2 or 1)-bytes/per packet transmission overhead rather than 37%.
    • Negligible encoding/decoding overhead.
    • The ability to read for just what is required rather than rely on buffering and buffer management.
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom