Re: The Truth About EGL

Aaron,

The machine I was using and measuring the 2 millisecond metric (in the request-response cycle) was my model 520 which has a 3100 CPW rating, and that particular database maintenance model links one user session to one i5/OS job, similar to 5250. The user session runs within a portal, which is one more job which is launched by an operator issuing a command from the command line, or activated through a scheduler, but the portal uses an interface where a single job supports multiple concurrent users (must save and restore user state at the beginning and end of the request-response cycle).

Joe Pluta also asked a question about Lan vs. Internet. There is a lag in the end user response time over the Internet, but even over the internet the records fly across the screen at a rate that's humanly impossible to read. When a user presses and holds down a key the highlight bar moves from row to row in the list at the speed of the PC because that interaction is handled locally. Each row advance triggers a request to retrieve the complete matching record from the server to display in the detail frame, but under my architecture the requests are queued, and under the reduced bandwidth of the Internet the refresh of the record in the detail frame lags behind navigation in the list frame. If the user releases the arrow key, it may take a couple seconds for the interactions in the detail frame to catch up.

Nathan M. Andelin




----- Original Message ----
From: Aaron Bartell <albartell@xxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Wednesday, December 19, 2007 7:29:31 AM
Subject: Re: [WEB400] The Truth About EGL


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






____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs