> There's a give and a take. You have to decide what's
> ultimately the most
> important. As for performance and tight programmatic control
> JSP seems to
> be better. If you require a quick time to market, ASP is
> probably your best
> bet.
I would be to differ. JSP is much easier to use than ASP if you know Java.
If your more a Windows/Visual Basic person than ASP will be easier. I find
JSP much easier to work with and offers a lot more than ASP does in the way
of functionality. You get the full JDK available (if you want), as well as
the power of using it on any platform (as you said) which can ultimately
give you much more powerful servers, thus increase performance, reliability,
and scalability. COM is inherently more complex to work with than JavaBeans
and EJB, although EJB isn't a piece of cake either. Even is ASP+ is compiled
into some format, its still tied to Windows, while your JSP code can move
not only to any platform, but to any app server that implements J2EE on that
platform. So now you are free to choose the platform AND the software to run
your code with. Plus, I am quite sure Java/EJB is, or will soon have much
more support for enterprise development than MTS/ASP/COM/DCOM. There is a
reason Java is now the #1 sought after development language and a large
number of companies are flocking to J2EE. J2EE is made up of many big
companies (and many small ones), while MTS/ASP and all that jazz is strictly
MS. This is one place I think MS wont come close on. They have lost this war
of enterprise solutions in my opinion. There are still a lot of people that
are solid MS and anti-java, but there are a lot more realizing the potential
for java based solutions.
> 1. Performance (support for high hit rates)
>
> JSP is better. It compiles to servlets instead of being line-x-line
> interpreted. BUT, ASP+ should do this as well when it comes
> out. You also
> have the option of not running on NT which can mean you'll
> potentially see a
> performance boost.
Agreed.
> 2. Ease of Development
>
> Not too bad but not nearly as easy as ASP. The syntax is
> more complex, and
> some things that would normally take 1 linein ASP, take many
> more in JSP.
> Retrieving a simple cookie for instance. On the other hand,
> Java offers a
> great number of resources inherently. On the other hand,
> with ASP you have
> some pretty amazing products like SiteServer you can rely upon.
Disagreed. JSP is easier if you know Java. ASP is easier if you are a Visual
Basic guru. JSP does look cleaner in an html editor than ASP does if you ask
me, but that is my opinion.
> 3. Ease of Maintenance
>
> That all depends upon how you architect your project.
Agreed. If you follow MVC where you use JSP for strictly a view of data, and
let the server side servlet and actions do the controlling, while EJB does
the logic, your set!
> 4. Development Time
>
> ASP was built for RAD development; a cousin of VB - one of
> the all-time
> great RAD tools.
That will soon change with JSP 1.1 aware editors. Drag and Drop of beans
onto html pages wont be far from now, with maniuplating tags (JSP 1.1) and
beans and their properties. Also, you'll have alot more tag solutions for
html pages with JSP that you can drop in for such things as iterations of a
list of items, a drop-down selection box based on dynamic input to the list
of the drop-down and the selected item(s), and so on. Unless I am mistaken,
I don't think ASP supports any type of special tags like the tag-lib support
for JSP 1.1. I think for an html person it will be much easier reading JSP
tag-lib in the page than ASP.
===========================================================================
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
