CGI tends to get a bad rap (often rightly so) because it's based on the concept of one request per process lifetime. Creating a new process for each request is part of what makes CGI apps so easy to create, you don't have to worry about multi-threading issues or worry about the state of the process, it's always new. Think of CGI as being RPG calls where you seton LR after each call, it's slower, but it's always clean. :) There is also Fast-CGI, which is roughtly akin to calling return w/out LR in RPG :) Apache support FastCGI in general, but I don't know about the i5/OS version. More "modern" app servers support multiple requests as threads in a single process (or group of processes, often called a web-garden) but apps that aren't multi-thread capable can cause problems in these situations.
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx <mailto:WaldenL@xxxxxxxxxxxxxxx>
http://www.TechSoftInc.com <
http://www.techsoftinc.com/>
Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
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.