Re: CGI vs JSP...

<snip>
> On most platforms this is very expensive.  It'd be like submitting a
new
> job for every RPG program you run, waiting for it to finish before
doing
> the next step.  The overhead of submitting the job is significant.
>
> However, on the iSeries it isn't such a big problem because the CGI
jobs
> remain active and are re-used.  You don't have to start new ones over
and
> over.  Plus, iSeries programs can remain in memory with their files
open
> and variables intact so that they can be called again very quickly.
In
> RPG we think of this as ending with *INLR = *OFF, but it's available
via
> activation groups in other ILE languages as well.  Since no other
platform
> has this functionality, and iSeries is such a tiny niche of the
market,
> this is still considered a huge blemish on CGI in general.

I'm going off of memory on this one, from posts by Andrew Borts on the
ignite400.org list.  He had (has?) an extremely active site and was
complaining about the expense of upgrading his systems to do the
webserving.  Now this was a few years ago, so maybe the less expensive
boxes have enough horsepower to handle even the most active of sites.
<snip>

I remember this discussion very well but the problem wasn't so much the
hardware as the HTTP server. The Original HTTP server had some real
scalability issues with CGI (I ran into those myself right before we
switched over) but those have pretty much gone away with the Apache
based server.

Matt