RE: HTTP Server's jobs for CGI applications

> 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!

I think so to!  And I understand your point.  Here's something to think
about.

The same people that know enough abut cookies and javascript to be worried
about it are the same people that know how to spoof a form field or even
easier, query string data.  Just something else to think about.

90% of the population (non IT folks) get the message "accept cookie" and say
"huh?"

Brad
+---
| 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
+---