Typically persistent CGI jobs are used for code written in "5250 style" i.e. All file positions, variable content, etc. is retained between calls just as a green screen program normally does. No need to code in a stateless manner or to store/restore state information with each transaction.

Often used by tools that are re-purposing green screen code to the browser.

Jon P

On Aug 23, 2022, at 11:30 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I'm not sure what you mean about making the CGI persistent.


So that the program stays running within the job?

Yes. The job is dedicated to a single user. Program remains active. Files
remain open.

That would mean extensive recoding
and how would it help with multiple simultaneous http requests?

Multiple simultaneous HTTP requests are handled by multiple CGI jobs.
Similar to telnet. One user, one session, one job.

I doubt the interface would require substantial re-coding. But I may not
understand your use-case.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.

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