I figured I'd throw my $0.02 in since I saw some mistruth spoken about this:
ASP code gets compiled by IIS and gets stored in its memory cache. I
wouldn't say compiled into C++, but whatever internal mechanism the MS
decided to do -- I haven't heard exactly what it is). ASP allows the use of
ActiveX COM objects (C++, VB, Java, etc.) which are _definitely_ compiled.
A proper ASP application should always be using ActiveX objects to performs
the majority of the business logic. ASP is good for the presentation layer
-- just like JSP. IIS handles these ActiveX objects very efficiently, the
object gets cached by IIS and then it just needs to create a new instance of
it for another session (that is, if you use sessions). The DLL gets loaded
into memory and then resides there -- it doesn't need to reload it for each
subsequent instance, nor does it reallocate more memory for another complete
instance of it (only allocates memory space for the object, not all the
DLLs).
I'm almost positive the ADO stuff will be quicker than JDBC. I haven't
tried it yet, but I'm going out on a limb and thinking that native compiled
stuff will run faster than the Java. Call me crazy. Object initialization
might be quicker in JSP than ASP though. ASP will not be doing in-line
object declaration which you can do in JSP, i.e.
ASP: Dim objFoo
Set objFoo = Server.CreateObject("My.ActiveX")
JSP: MyBean foo = new MyBean();
so JSP might have an edge there.
As for the REAL numbers, I've run some tests. I'm not going to post them
because they will always differ for what you are going to try to do with it.
Besides, I might get in trouble. :-) Anyway, for those who run with NT,
you can always use WCAT (web capacity analysis tool) which is part of the
IIS Resource Kit. Don't worry its a generic tool which you can configure
loads onto ANY web server -- not just IIS. So it won't skew the results for
MS specific products (if you were wondering). Also, there is another tool
called WebLoad (http://www.microsoft.com/gallery/tools/radview/webload.asp)
which can simulate loads as well, and is a free download off MS Sitebuilder
Network.
The real gain from either one is the implementation. What skills do your
engineers have? Which one helps you write more bulletproof code? Since
they are VERY similar, the choice between one or the other isn't black and
white, but more like shades of gray. For something that needs to be done
quickly and used in a production environment, I would definitely say ASP
would win. Its a proven technology used in MANY sites (I'm sure you don't
need me to quote some). Since JSP isn't even at 1.0 yet, it certainly puts
a much greater risk factor in its use. However, six months to a years
later... Who knows? If Sun releases their spec and its decent, then JSP can
prove itself in time as well. I know I wouldn't be risking my career to
choose a technology/specification that isn't even finalized yet. You can
always write your ASP using Java objects for your business layer and port
the whole thing over to JSP when you think its ready.
I've done a lot of ASP applications which get a high number of users. If
you do it right, the speed is fine. I'd like to be using JSP since its just
easier to be doing everything in one language (i.e. Java) rather than this
VBScript and Java stuff (ASP code and Java COM objects). So when reading
the above info, take it in context of where I'm coming from.
___
Michael Dinsmore
Sr. Engineer/Architect, Passkey.com
mailto:[EMAIL PROTECTED]
phone:617.328.4800 x230
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
