|
I agree about persistence...
Users yell when their sessions timeout...
Sorry for derailing the original topic. That was not my intent. I have
never used persistent CGI. But any site that is totally stateless is also
void functionality and likely performs poorly too.
The best performing and most functional sites may maintain state in
QZDASOINIT or QSQSRVR jobs, or possibly ILE jobs which process requests
coming in on data queues, or some similar architecture.
Why characterize "stateless" as an advantage? It's certainly not a panacea.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
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
