Scott Stirling wrote:
>
> I got the point of the non-JSP alternatives being available and
> perhaps overlooked.

Glad to hear it.

> I also got the one that JSP shouldn't be seen as the logical
> replacement for servlets.

Also good.

> But I didn't like some of the red herring and
> straw man arguments used to try to bolster the points, for example:
>
> 1. When a standard taglib becomes part of the 1.2 spec., most
> or all of the arguments about the complexity and ugliness of JSP
> will be invalidated.

Be careful not to count your chickens before they hatch.  This
standard taglib has yet to be written.  We all (myself included)
are going to try to make it the best it can be, but the reality
is almost always less ideal than you imagine.

> It's short-sighted to rely on an argument to the contrary.

I made clear in the article where a standard tag library would help
out.  I also pointed out that such a library has yet to be written.
Not even a little demo one yet that I know of.  That makes me suspect
it's a hard task, but more importantly it implies that we're blazing
new ground here and may not yet know enough about this technology area
to define a good standard.  We all know it's hard to make an early
implementation the Right implementation.  I'm not saying it can't
happen.  Just be realistic.

> 2. The memory argument was a particularly memorable straw man.

It's interesting you say that right after Tom Reilly wrote:

  My main concern is memory consumption. Someone else pointed out
  that memory is still fairly cheap, but in general I dislike
  an architecture where things can never be unloaded from memory.

Considering that some people view it as a problem, it belongs in an
article titled "The Problems with JSP".

> Another note: EJB.  Sun and lots of other companies are stoked
> about EJB.  I think they see them as essentially RMI-based servlets
> that automagically handle transactions, security, safely synchronized
> concurrency, and lots of other features.  With servlets, programmers
> still have to handle all that crap.

EJB isn't a replacement for servlets/JSPs.  Someone has to speak HTTP.
EJBs are a way for complicated sites to design the back end that will
be used by servlets/JSPs to handle the front end.

-jh-

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html

Reply via email to