The session ID is nothing more than a cookie with an ID in it. CGIDEV2
has some good cookie manipulation functions.

Check if the cookie exists.. if so, use that value for the process. If
not, create a new cookie and use that value (making sure it's unique).
Stateful CGI is pretty simple in that regard.

And I would also advise not using QTEMP unless it's something done for that
request only (ie, the data is rebuilt each time) and you will never assume
that the next request will use that data again. You can't really count on
the same user getting the same HTTP Server job.


On Fri, Nov 4, 2016 at 4:02 PM, Roche, Bob <broche@xxxxxxxxxxxxxxxxx> wrote:

Maybe I was over thinking this. If I'm building a web page, until that
page is built I'm in a single job. Maybe I can be safe referencing qtemp at
that point. I have to remember all these separate functions in PHP are
still being called by one program. I'll get the hang of this yet.
I was worried about using a persistent connection. This is an internal
company page, so there is no actual login, it is using a default id for
connecting for all users. So I don't completely understand how it maintains
the state. My prior web programming experience was CGIDEV2 all programmed
for a stateless environment.

I'll get the hang of this yet.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.