RE: HTTP Server's jobs for CGI applications

I'm grateful to Hans, Brad, Leslie, and others who have contributed to this
thread's debate.  For me, at least, the issues discussed are timely.  I was
just starting to encapsulate some code to make it easier to write HTTP
Response-Headers (such as Cookies).  I had been planning on using Cookies in
my next web application to help track session variables.  Now, I'm not so
sure.

If you are creating a public site, you need to consider the site's
accessibility to a broad range of users - including those who disable
Cookies and JavaScript.

After reading the debate and following up on the links provided, I've
concluded that Han's viewpoint is not paranoia.  Its rational.  Not to the
point of motivating me to disable my browser support for Cookies and
JavaScript.  I'm willing to risk some invasion of personal privacy in
exchange for my use of the many popular sites that depend on Cookie and
JavaScript mechanisms.

But, for those of us who build web applications for public use, its not much
harder to store a "Session ID" in a hidden "Form"  variable, or append it to
the end of a URL as a "Query-String" variable.  Then retrieve it on the next
Post or Get operation.  I tend to use a Session ID to then retrieve session
related variables stored in a database.

This has been an interesting debate!



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---