RE: beans and JSPs and stuff...

But such changes can only be made in CGI through programming the host side.  In 
a JSP environment, most web presence changes can be made without touching the 
host logic.  With the CGI approach, every change in the presentation, from 
trivial to extensive, must be done through the CGI programs.

The only way around this is to write a CGI program that in essence reads a 
specialized HTML page and plugs in your dynamic content wherever it's needed.

And that's... a JSP!

Also, the speed of a JSP is exactly the same as that for a servlet, since a JSP 
is a servlet.  There is an initial compile time for a new JSP, or when the JVM 
is first fired up.  That can be reduced by preloading JSPs as necessary.


---------- Original Message ----------------------------------
From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
Reply-To: JAVA400-L@midrange.com
Date: Tue, 27 Feb 2001 11:00:37 -0600

>That makes sense, but it could also be done with SSIs, servlets/CGI.  I'm
not saying JSP is not a good way to do it, because it is.  I'm just saying
there are other ways.  I tend to lean towards SSIs because they're so
"modular".

Brad

> -----Original Message-----
> From: Larry Loen [mailto:lwloen@us.ibm.com]
> Sent: Tuesday, February 27, 2001 9:22 AM
> To: JAVA400-L@midrange.com
> Subject: Re: beans and JSPs and stuff...
> 
> 
> 
> Brad Stone asked:
> 
>    Or is JSP really an advantage?
> 
> One advantage someone pointed out to me was that it would
> be fairly easy, with a JSP-based design, to have a multi-language
> strategy.
> 
> You know what I mean, I trust:  The kind of site where you
> push a button or a link and it takes you between the English,
> French, and German (etc.) version of the web site.
> 
> This depends a little on what the Java "widgets" do,
> but one could imagine that if the "widgets" mostly did
> custom imagery or simply rendered data bases in tables
> and like things, that one could have virtually all the 
> language-dependent
> elements in the JSP, managed by web-designers (or, at least
> those with minimal programming skills) and the rest done by
> the Java programmers, largely in their own language.
> 
> Thus, JSPs could largely if not entirely isolate the whole
> "national language" question from the programming source,
> proper, which everyone wants.
> 
> BTW, Javascript means that many web designers have a minimal
> understanding of programming -- enough to deploy a JSP, I would
> think.
> 
> 
> Larry W. Loen  -   Senior Java and AS/400 Performance Analyst
>                           Dept HP4, Rochester MN

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---