The receiver is going to need to know when it has received a whole message. The following does so by prefixing the data with the length of the data.

Sender: 

my $msg = pack('N/a', nfreeze($data));
while (length($msg)) {
   send_msg_block(substr($msg, 0, $max_msg_size, ''));
}

[download]

Receiver: 

while (length($buf) < 4) {
   read_more_into_buf($buf);
}
my $data_len = unpack('N', substr($buf, 0, 4, ''));
while (length($buf) < $data_len) {
   read_more_into_buf($buf);
}
$data = thaw(substr($buf, 0, $data_len, ''));

[download]

This doesn't address the issue the anonymous monk raised about UDP. That's for your send_msg_block and read_more_into_buf to handle.

In reply to Re: Chunked Perl Serialization by ikegami
in thread Chunked Perl Serialization by viral

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.