RE: HTTP Server's jobs for CGI applications

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

There is a session ID that is unique for each HTTP request.  Find out how to
retrieve this and use it where you can.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: Bob Cozzi [mailto:bobcozzi@attglobal.net]
Sent: Friday, July 14, 2000 6:33 AM
To: MIDRANGE-L@midrange.com
Subject: HTTP Server's jobs for CGI applications


I'm a little confused, perhaps people on this list would know for certain
what's happening.

Does the HTTP server on the AS/400 create a new job for each user of the web
site. Specifically, I'm trying to determine if a CGI program that is called,
can create a temporary object in QTEMP and use it. My concern is that if
another user enters the same page at the same time, they will be colliding
with previous user's temporary objects.

If each user is routed to a distrinct job on the AS/400, then I don't have a
problem.

My situation is that I need to create either an outfile or a user space that
is unique for a CGI evocation. I'm worried that if every CGI request is run
in the same job, then everyone would see the same temp objects. This would
be bad. So I need a way to create temp objects that are unique for each CGI
request.

Caveat: On the otherside of the coin, if each request is in a distinct job,
how many jobs are created on an AS/400 when there's a million hits per day?

Bob Cozzi
+---
| 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
+---