Overall, good stuff. But I think you better doublecheck
that "Perl will read a few bytes ahead to improve
performance" claim. I don't recall coming across that
anywhere else before. In particular, I've used
print and <> with sockets before
with no problems. The key is to not mix them with
sysread and syswrite.
Also, I think IO::Socket and IO::Select deserve more space.
After becoming comfortable with them, I far prefer them
over the raw Perl stuff, which looks more like C than Perl.
There's a good example of both IO::Socket and IO::Select
at the end of perldoc IO::Select. Of course, it should be
noted that the major limitation of IO::Select is that it
doesn't allow you to wait for reading,
writing, and exceptions simultaneously. You have to pick
one. But, for the example you show, that's not a limitation.
Finally, one minor thing: "get all the data it wants before
continue" should be "...continuing".
But, overall, pretty good stuff. Have a Scooby snack on me.
*Woof*
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, 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, 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.
|
|
