|
When the CGI program returns, the A/G remains in memory. If another CGI request comes in (from the original
> client or another one) and that same CGI job is called > upon to process this new request, then A/G and
therefore the program is already in memory,
> and starts running.Is there a guarantee that all CGI requests will be served by the same job? In other words, is it possible for OS/400 to start multiple jobs, and therefore have multiple AGs?
This is crucial if one intends to use the AG to store state between CGI requests. It sounds like the OP is tweaking performance, in which case it's a moot point how many jobs OS/400 creates to service CGI requests.
--buck
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.
midrange.com
