With the caveat that this is based on dim memory, I futzed around with
HTTP::Daemon a few years back, and recall that getting
Connection: keep-alive working took a combination of
- making sure that sockets were unbuffered, and
- generating an accurate Content-length: header.
But, unless you can fork, or otherwise multiplex I/O, you're liable to see strange browser behavior, since most browsers (or at least IE, since the early days) try to use two sockets at once to optimize page and image transfer. You also have to worry about the cause of a browser asking to keep a connection alive, and then, for whatever reason, not using it again.
I think what I ended up doing was to punt on http-alive, and fall back to HTTP 1.0 behavior. It was good enough for what I was doing at the time (which was putting a custom, low-bandwidth web server up on a machine that I didn't have administrative access to).
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.