From: Aaron Bartell
Now you have my curiosity getting the best of me. You don't
mind considering REXX but you are fairly adamant about RPG
not being in the picture. I just have to know why :-)
Dave has expressed his opposition against RPG in many other threads, and it's probably useless to try to persuade him differently.
There are many reasons for using RPG for Web applications, but one that I weight highly is performance. To illustrate I took a couple screen shots, one of which shows Firebug's console, tracking POST and GET operations from a sample database maintenance application I generated.
I'm in the middle of making and testing changes to the model and code generator, and needed a quickie application to test with - but that's another story...
I got a new perspective of performance by recently downloading Firebug and seeing it automatically tracking the time (in milliseconds) to complete the browser request-response cycle, and I began noticing the time required to perform database updates (Add, Copy, Change, Delete) and single record fetch operations.
In this sample, which admittedly is trivial, the time required to complete various POST and GET operations which update the screen ranges from 32 - 47 milliseconds. And that's elapsed time, which includes time on the wire. With performance like this, it seems to me that there's a case for using RPG for heads-down data entry, transaction processing, and any application where users demand top performance.
If you're interested in the screen shots, see:
http://www.radile.com/rdweb/temp/tst100.html
Nathan.
midrange.com
