Re: Reusing User ID and Password with Zend i5_Program_Call

Apache is responsible for the forking. When it starts up it will
pre-fork X number of processes prior to servicing HTTP requests.

The process, not the request, "owns" the connection. It's a slight
difference in terminology, but might clarify it a bit. So if you have
10 forked Apache processes, then you will have 10 connections, once each
one has created at least one connection. If you are serving 1 HTTP
request and have 10 Apache processes, you will still have 10
connections.

Kevin

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Walden H. Leverich
Sent: Thursday, June 11, 2009 9:17 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Reusing User ID and Password with Zend
i5_Program_Call

OK, if I've got that then a given request will be processed by a given
"pre-forked Apache process" and have access to that connection? Then
where does the forking come in? Also, if I described it correctly then a
request "owns" a connection for the life of the request, even if
database IO is only a fraction of the request time, yes? 10 simultaneous
requests == 10 connections to the i.

-Walden