Phil,
JSP Advantages:
More reliable, (ASP may look like it works but JSP/Javabeans mean
you have to catch exceptions i.e. better code) - When you implement the
data access and business logic in compiled languages this difference has a
far less reaching effect; in essence, your "better code" only applies to the
User Interface.
Faster ( really ) - I think this is highly debatable. With a C++
data access and business logic tier driving the ASP I think you will find
the Microsoft Architecture to be considerablly faster and more scalable.
Object Oriented ( finally reusable code ) - C++/J++
You can use a Debugger ( try that in ASP ) - Although this is a lame
answer, check out Windows 2000 Server. This problem goes away.
run anywhere etc, - Very true but COM does give you the ability to
run J++ COM Objects that can run anywhere as well.
Tags - don't know exactly what this means.
Easy DB Connection Pool - Also true of 3 tiered architecture
Complied Code ( Clients can't nick the source ) - Also true of 3
tiered architecture except UI logic.
JSP Disadvantages
require more expensive, good programmers where as monkeys can
program ASP - Good people are hard to find in any language.
Although I can see considerable advantages to developing in JSP for
organizations that support multiple platforms and large complex applications
that would be greatly benefitted by an object oriented language, this is
also possible to do in a Microsoft Architecture. I like JSP for many
reasons; however, you are not really comparing JSP to ASP. You are
comparing JSP to ASP connected to COM connected to C++, VB, J++. From a
manager's perspective (although I am not one) I can see many advantages to
this.
- My less experienced programmers begin writing ASP and writing the UI logic
for the application. UI logic tends to be straightforward.
- My middle level programmers develop intranet functionality for the site
(such as Content Creation Tools --possibly this is done in VB).
- My expert programmers code the business logic and data acess in my
language of choice. Possibly you use some C++ and some J++ programmers
based on availability in your market or appropriateness. For example, C++
really smashes all alternatives when it comes to mathematical operations.
The cost of this infrastructure is less, the solution is still platform
indepenent, the application is highly scalable and I can use my best
programmers where scalability is key, and I can mentor my younger problems
into brilliance.
It is ironic that I am making these arguments and simultaneously trying to
learn JSP to become more involved with complex and enterprise wide
solutions. I don't find these subpoints to be yeah buts, instead I believe
that they are solutions for small and mid sized businesses and less so far
large corporations.
Before I end, let me beg to not be bombarded with e-mails. I am just trying
to make sure the comparison is done with all the arguments present.
Clearly, I find a lot of advantages in JSP or I wouldn't be working so hard
to learn it.
Thanks,
Devon Manelski
MCP
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Phil Campbell
Sent: Friday, July 07, 2000 1:02 PM
To: [EMAIL PROTECTED]
Subject: Re: FTP From JSP
Thanks, Devon... informative discussion on possible situations where
Microsoft's asp might be acceptable.
Hopefully any Microsoft IIS lovers will forgive my reference to Cleopatra's
asp. Companies usually spend much effort to avoid such comparisons with
branded names and technologies. MS overlooked the obvious.
It's interesting that dangers of developing in unsuitable environments is
like handling a venomous snake. Considerable time is wasted in avoiding the
probable and mending those resource-bites as they happen...
MS' arguments that ASP may perform well in certain environments (MS NT IIS
with MS SQL 7) seem reminiscent of PC developer's defending dBase...
ultimately, product viability rests in advantages, not in yeah'but
arguments.
Do you believe that Graham Cruickshanks' list of JSP v. ASP pros and cons is
accurate?
Can you add to the JSP disadvantages list, or think of any ASP advantages?
Phil
-----Original Message-----
From: Devon Manelski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, July 07, 2000 10:21 AM
Subject: Re: FTP From JSP
>Phil,
>
>Could you outline your concerns regarding ASP and JSP? I think both
>languages are appropriate given the nature of the existing hardware,
>software and staffing infrastructure. Your performance requirements and
the
>complexity of the application also affect the decision.
>
>Although there are inherent limitations of scripting languages (such as
>ASP), the correct architecture can help to reduce the cost of this
>shortcoming. The point made regarding the optimized relationship of ASP -
>IIS - COM - SQL Server 7.0 is also significant. Microsoft has corrected
>their original assumption that ASP can be used to build a complete
>application. Instead they now propose that your data access and business
>logic are done in compiled languages such as VB, J++ or C++. The UI logic
>is really what is done in ASP.
>
>It all depends on the specifics of the application and organization.
>
>Devon Manelski
>MCP
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
