Tcip/ip is a transport layer. It is a way for the client to shovel data bits into a pipe and for the server to read those bits. This lower level protocol ensures that the bits that I send is what you get.
The next level higher is like: how many bits from you constitutes "one thing"? Maybe a fixed 256 bytes constitutes one "message". Maybe some string of characters which end in "\n" constitutes one "message". Maybe some number of lines that end in "\n" and a null line "\n" after all of the relevant lines constitutes collectively one "message". This is part of how the client "talks" to the server.
This is client<->server message protocol specific. Perl is great at "\n" terminated messages! I print one line to you and then I receive one line back. Perl can also deal with fixed byte length message packets.
Anyway all of this is related to the application I/F between client and server.
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.