Your point is quite right I think. There are certain weaknesses built into HTTP that makes session management more difficult, though I don't know if I would consider all solutions kludges.
From an enterprise developers point of view, so long as you wrap a kludge in a strong enough component with a cler enough public API, then that is fine.
CGI.pm does a wonderful job at this and I am proud to say that Lincoln took comments from Gunther and me, while we were at the NIH Genome Project, when designing it.
That said, I equally enjoy working with Servlet Containers.
In the end, once objectified, so long as the kludge works, provided it is a black box to me and works, as a developer, then I am more or less satisfied.
I don't know if I would geive up HTTP though. I may just be old fashioned, but I rather like it as a standard.
- Selena Sol
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.