Typically connection pools are not done in PHP because of the
"shared-nothing" architecture. In other words, individual HTTP requests
are isolated from other HTTP requests. Connection pools are possible by
building in a pooling layer and then a separate daemon, but they are not
part of the language since that would break the concept of the
shared-nothing architecture. I have some base code that I have been
toying around with that could be a base for it(and just came up with
another idea while writing this sentence) but it would not be
engine-level (nor, I would argue, should it be). Time is also a factor
:-)
Kevin
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Nathan Andelin
Sent: Thursday, June 11, 2009 8:33 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Reusing User ID and Password with Zend
i5_Program_Call
From: Kevin Schroeder
Another mechanism would be to use PHP sessions to store the
username and password on the server side.
It's interesting that this suggestion has come up several times, but
that no one has yet suggested maintaining an IBM i connection in some
sort of pool for the duration of the session - just storing the
connection ID in the session - rather than storing password. That
puzzles me. I've never done any PHP coding, but using some sort of
connection pool was the first thing that came to my mind - forget the
password after initial login. What am I missing?
Nathan.
midrange.com
