RE: Database Maintenance Models

> From: Nathan Andelin
> 
> > One technique I use is a servlet proxy that is not
> > multithreaded that established a connection with a
> > batch job.
> 
> That's better.  The Servlet presumably hands off significant
processing to
> a
> separate job, freeing up the container to dispatch similar work to the
> same
> proxy in a separate thread.  Are you careful not to perform
significant
> workloads in your proxy?

<grin>

You know me better than that, Nathan!  The workloads are done by an RPG
back end, of course.  Depending on the model (client/server vs.
server/client) the RPG may also be doing the application control (that
is, determining which panel to display next).  Either way, the servlet
proxy usually does little more than convert EBCDIC messages to beans and
hand off control to a JSP.

This is the sort of thing I really want to get into at the application
web site.  Seriously, the choice of architecture is going to be crucial
as to the choice of technology components (and vice versa).  I think
we're going to find that there are multiple routes to the same goal that
will use slightly different techniques, but still meet the business
requirements of a given case.  I have to believe that a properly
designed JSP/servlet solution has many of the same characteristics as a
properly designed CGI solution, and that the choice between them will be
a bit more subtle than simply "Java vs. RPG". 

Joe