Here's a posting to this group from about 2 months ago. I found it really interesting.
=============================================================
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 9 Nov 1999 09:52:17 -0600
Reply-To: John Hardin <[EMAIL PROTECTED]>
Sender: A mailing list about Java Server Pages specification and
reference <[EMAIL PROTECTED]>
From: John Hardin <[EMAIL PROTECTED]>
Subject: Re: JSP vs. ASP
Comments: To: David Geary <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-UIDL: 68315d32d216eb45e53366a8a21bd7ac
This was alluded to in other posts, but wasn't explicitly stated; so, I'll
give it a whack.
"Shared" code is accomplished in ASP via #include'ing other source files.
The problem with this is the ASP compiler processes all of a file's includes
into a single source file, and then compiles that file. If you really *do*
share this code (perhaps all over your site), then the shared code will
effectively be replicated in *each and every* compiled ASP page. JSP, on
the other hand, will only have *one* copy of the compiled shared code in its
VM.
(Sharing can also be accomplished through Server-side (COM) objects, but the
relative performance of these objects (versus Script code) -- believe it or
not -- stinks.)
To make this even worse, IIS's controls over the ASP file cache *stink*.
You get 3 options: don't cache anything (yeah, right :-), cache everything
(again, I'm sure :-), or cache N files. What they're lacking is an option
that says cache as many files as possible using no more than X bytes of
memory. IIS, with the given options, will run itself into oblivion trying
to cache the specified number of files -- even if it runs out of memory in
the process.
Where you can easily and non-obviously get hosed by this is when you expand
your shared code. Suddenly *every* ASP page that uses the shared code gets
bigger. And unless you proportionally *reduce* the number of ASP files that
IIS tries to cache by the proportional *increase* in the resultant ASP file
size (due to the expansion of the shared code), then IIS may well run itself
into the ground trying to cache the specified number of files.
And since there aren't any good tools to even *know* how big your compiled
ASP files are, you end up doing a lot of experimentation and/or throwing
lots of memory at your web servers.
Oh and one last thing. ASP files have to be recompiled after you reboot
your web server. JSP files are compiled once, and then simply reloaded into
the JVM after a reboot.
-jwh
> -----Original Message-----
> From: David Geary [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 05, 1999 9:02 PM
> To: [EMAIL PROTECTED]
> Subject: JSP vs. ASP
>
>
> I just finished reading Sun's "Comparing JavaServer Pages and
> Microsoft
> Active Server Pages Technologies" article from the Java Web
> site -- see
> http://java.sun.com/products/jsp/jsp-asp.html.
>
> The article claims that Java provides superior performance over
> interpreted scripting languages. Of course, the article fails
> to mention
> that compiled servlets are byte code that also gets
> interpreted. So, is
> there any validity to this claim? Does JSP provide a noticeable
> performance increase over ASP?
>
> Memory management and exception handling are also cited as JSP
> advantages. This seems like a legitimate claim to me. Are there any
> former ASP developers on this mailing list that have run into problems
> stemming from misbehaving applications crashing servers because of
> memory mismanagement. Have any of you former ASP developers found
> yourself cursing ASP because it lacked exception handling?
>
> The article implies that JSP emphasizes components over
> scripting, which
> makes it easier to revise content without affecting logic and vice
> versa. However, it seems as though ASP is just as "componentized" as
> JSP; after all, ASP can use COM objects and JSP can use
> JavaBeans. Am I
> missing something here? Is JSP somehow more component worthy than ASP?
>
> Speaking of components, I would venture that COM objects are more
> plentiful and mature than JavaBeans, which would give ASP an advantage
> over JSP. Is this a valid assertion?
>
> As far as I understand, ASP does not provide a customizable tag
> mechanism as does JSP. Is that the case? Does anyone know if Microsoft
> plans to add such a feature to ASP in the future? I can see that a
> customizable tag mechanism would be beneficial, but how big
> of a deal is
> it? Does anyone care to comment on how they are using
> customizable tags,
> and how miserable life would be without it?
>
> Of course the biggest advantage of JSP over ASP cited by Sun
> is the fact
> that JSP is platform independent, and therefore more widely
> supported by
> Web server and application server vendors. However, there are
> companies
> that have developed plug-ins for servers other than Microsoft
> servers to
> run ASP. In light of that, how big of an advantage is JSP's platform
> independence?
>
> JSP is language specific but platform independent, whereas ASP is
> language independent and platform specific. Language independence is
> probably quite an advantage for companies with legacy systems, whereas
> platform independence seems to be somewhat of a dubious advantage
> because of the fact that software can be purchased to run ASP on non
> Microsoft's Web servers. Comments?
>
> Finally, I'd love to see a show of hands from former ASP
> developers that
> have moved over to JSP, with a short explanation of why you made the
> switch.
>
>
> david
>
> ==============================================================
> =============
At 11:06 AM 1/6/00 -0800, Edward Pearson wrote:
Hello list! This is my first posting and I'm a newbie to JSP. Actually, I=========================================================================== 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
know very little about it. We're using NT servers and running Active Server
Pages (ASP) web applications with SQL 7.0 as our back-end database server,
however, we're not thrilled with the performance. I'm wondering if anyone
could shed a little light on whether JSP would be a much better choice than
ASP. Thanks!
Edward Pearson
Web Developer
www.ninthhouse.com
===========================================================================
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
