I'm trying to write a test server to work with google chrome's native messaging. all messages are passed as a unsigned 32-bit number followed by that many bytes of utf-8 encodes json.

Ok so I read 4 bytes, and unpack my length, read length bytes and decode using utf8::upgrade and a json parser (tbd). And I take the response I generate, encode it as json determine length, and pack.

But the devil is in the details. perldoc -f pack is unclear as to the size of 'i'. Some places it appears this may vary by processor, and could be 32 or 64 bits. other places imply that it is 32 bits only. Also I am uncertain as to the best way to encode the response string should I use utf8::encode, pack, or something in Encode::

Your advice is appreciated.

In reply to native byte order integer and utf-8 by bhildred

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.