One option you have is SQLRelay
(
http://sqlrelay.sourceforge.net/sqlrelay/). I have not worked with it
and cannot vouch for its viability, but I have heard of people deploying
it to production environment. I have another thing in mind, too, but I
need to confer with some Zend people on it.
Kevin
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Walden H. Leverich
Sent: Thursday, June 11, 2009 3:45 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Reusing User ID and Password with Zend
i5_Program_Call
1,000 users could lead to 40,000 permanant connections
Yuck. I see your point. Not bloody likely, but since the connection is
user-job scoped, if the given user walks through each of the 40 jobs
then he will have a connection in each of the 40 jobs. Multiplied by
1000 users, yes, 40K connections, in theory.
And I sometimes store Last-Update-User, and show it on screens.
A feature like that would take a hit.
Only takes a hit to the degree that you count on the DB to populate. If
you put the population in your DAL then you can stuff in anything that
makes sense. We track last-update-session on our tables. We can tell you
not only who, but when they logged in and from where for that update.
:-) But it is plumbing that needs to be written, it's not "in there."
Your point about journals and other system-level stuff (jobs, spooled
files, etc.) is well taken though.
-Walden
midrange.com
