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