|
midrange.com
Bob,
No, a unique job is not created for each user. You can't even rely on the
user getting the same job on two consecutive page requests. You have to
account for this when you design your programs.
I believe the "standard" way to handle this is to assign a unique "session
id" to each user when they start a web session. You can then store their
temporary information in a database file that is keyed by this session id,
or some other similar technique.
You then have to pass the session id around to your programs by embedding
it in the HTML or the URL. You should also look into the documentation for
"Persistent CGI" in the HTTP manual. I think that by using the techniques
documented the web server can do some stuff to help you out, but the basic
idea stays the same.
Hope this helps.
Mark Phippard
"Bob Cozzi"
<bobcozzi@attglobal To:
<MIDRANGE-L@midrange.com>
.net> cc:
Sent by: Subject: HTTP Server's jobs
for CGI applications
owner-midrange-l@mi
drange.com
07/14/00 09:32 AM
Please respond to
MIDRANGE-L
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
+---
+---
| 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
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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.
