-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The performance gain that you get with JSP is that the JSP code is
compiled into a servlet class file once and then serialized and
cached for the life of the JSP engine. It is true that the compiled
class file is interpreted by the JVM, but this is still faster that
compiling the code each time a request is made for the page.
In terms of JSP's component-based nature, JavaBeans are far easier to
deal with than COM. I have experience with Visual Basic, COM, and
some ASP. The version control nightmares I've experienced with COM
have left me running away screaming. When I discovered Java and got
past the initial learning curve, I became convinced that it would
make my development life much easier.
One bonus that I find particularly in favor of JSP is the object
oriented facet. If you don't like what comes out of the box, you can
easily "scratch your own itch", as it were, and build your own class
libraries. Also, the custom tags make the technology very
extensible. For instance, JSP 1.1 does not have tags built-in to
access EJB (as far as I know - somebody correct me if I'm wrong).
So, instead of writing the code over and over to get a reference to
an EJB and access it's methods, you create a custom tag to do it -
and boom, you're accessing an EJB as easily as accessing a regular
JavaBean.
Configuration management is very important, especially in an
enterprise setting. COM, and even more so, DCOM, is a nightmare to
configure on an on-going basis. You install a new version of the
operating system, or maybe just a service pack or some other,
unrelated software package, and you may have overwritten a .dll or
.exe that your COM object needs. With Microsoft closed-source
products, you don't know what the installation process does. You
will be far more able to get an open-source implementation of the
JSP, or even J2EE standard.
Which brings me to another point: J2EE (JSP/EJB etc.) is an open
standard. ASP/COM is closed. Open standards have advantages because
they are influenced by a consortium of industry leaders. Not just
one corporation. You asked if anyone knows if Microsoft plans to add
customizable tags to ASP. I would venture to say that they will only
to it if it's to their marketable advantage. If you choose a closed
standard for your architecture, you will be locking yourself in to
that closed window and have no option but to be at the mercy of that
corporation.
Just one guy's opinion. I'm sure there are others.
Steve Wamsley
http://home.earthlink.net/~sswamsley
- ----- Original Message -----
From: David Geary <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 05, 1999 9:01 PM
Subject: JSP vs. ASP
<< snipped >>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>
iQA/AwUBOCSGoZaPN/z+dlkyEQJjWACbB15Z8gSEeibqwGMK5cUNAuwyFAcAoLFp
2pKTuTeZ++bDWJQXF7N2mj3X
=QepT
-----END PGP SIGNATURE-----
===========================================================================
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
