If you have full control over the protocol and both client
and server implementation then I would consider a different
method. It would be possible to continue using a end tag, but
it can be difficult to do that correctly and reliably without
fiddling with various
selects and reading methods and hoping that piece of data
won't appear in the file.
Alternativly I would do what some protocols do and use a
message content length (in exact bytes) so that the reciver
knows exactly how much binary data to read, after which normal
operation can resume.
For this you could just add a line to the sender to like
print OUT "Size: " . (-s $file) . "\n"; and the
reciver can parse that line of data and use one or a series of read
statements to recieve exactly that much data.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.