That's really a decision you have to make based
on your deployment environment and on-going maintenance issues. It's
easy enough to do a shopping cart app with ASP and a newsletter with ASP +
XML but then you are stuck with using an IIS server. Many of the early
shopping cart apps were done with JavaScript and this gives you server
independence because all the processing is done on the client. I'm not
sure how well together JavaScript and XML work together, but my inclination
is a dynamic newsletter should be processed on the server. Java gives
you psuedo-platform independence (you have to install the appropriate
containers and JREs for the server and there are platform-specific issues
regarding the use of AWT and native methods), but certainly is more fluid
across architectures than any Microsoft-centric solution. Of course,
if you are developing in a Microsoft environment, you can choose whatever
you want and it comes down merely to with what you are most
comfortable. Be aware, however, that if you are looking at maintenance
3-4 years down the road that Microsoft is abandoning all present
technologies in favor of .NET (IE 6.0 does not support Java,
either).
Good luck!
Mark
I am a deeply superficial person. -Andy Warhol
This email was scanned with Norton AntiVirus 2002 before
sending.
----- Original Message -----
Sent: Tuesday, October 09, 2001 4:07
AM
I'm doing a project which involce doing
shopping cart, newsletter adding etc.
and i have very shallow understanding of java
technology. i have 5 months to finish this project. which technology
should i use? asp or jsp with
servlet?
