Hi all:
This isn't my strong suit but wouldn't stored procedures on the i5 solve
most of these problems? Send the stored procedure the parameters and
get back the results?
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Walden H. Leverich
Sent: Tuesday, October 21, 2008 3:09 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] sql in php with paging
I understand that if persistent connections are maintained for
each user, that may lead to many database connections, but what
resource constraint do you see?
Well, I guess that depends on the scale and audience of the application,
no? For an internal application if you just consider the web app as a
nicer version of a green screen app, but still for internal consumption
then I don't think you'll hit any limits. After all, if your i could
handle n-hundred connections before (as a greenscreen) then you should
be ok to handle n-hundred connections now as a web-app.
But... if this is an internet facing application then while the machine
may handle n-hundred connections what will happen when there are
n-thousand requests? Or n-million? Either because you're really
successful, or because of a accidential (or intentional) DOS attack.
Been a while since I looked at the system limits documentation, but I'd
think you'd need a decent sized i to handle 50K active jobs, probably
one of the largest for 500K active job (if even possible) and I doubt
any i would handle 5M active jobs.
-Walden
midrange.com
