Nathan, what size of machine are you running for the example you explained
earlier (i.e. arrowing for next records with sub second response)? And how
many jobs are typically running with that type of AJAX workload?
BTW, I have also been intrigued by OpenLaszlo (what www.gowebtop.com uses)
and have been pondering trying it out with RPG and AJAX. I know it is based
on J2EE, so my options would be to have a thin Java layer (with app server
obviously) making calls to backend RPG programs. What type of reliability
issues did you have with this? And did you implement the server side without
J2EE? (my lack of OpenLazslo architecture showing - might be straight
forward to spin ones own wool and create an alternative back end server in
RPG)
BTW, www.gowebtop.com is one of the fastest browser apps (over the internet)
I have used to date, VERY NICE!
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Walden H. Leverich
Sent: Wednesday, December 19, 2007 8:09 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] The Truth About EGL
Apache on i5/OS is able to reuse existing CGI jobs
Which is roughly akin to FastCGI, as you point out. And I'm glad the i5
does it better. But we're still left with the problem that there needs
to be a job for each active request, as opposed to a multi-threaded app
server (like WAS) where each request is handled on a different thread in
a common process. For smaller sites where the number of simultaneous
requests are low the one request per job model is fine, but as requests
ramp up (and ajax makes them ramp up fast) the model begins to show its
weaknesses.
-Walden
midrange.com
