My organization uses both servelts and ASP on occassion (we're mostly a
Cold Fusion shop).
In addition to the benefits noted by previous posters, you should note
the following:
ASP is relatively difficult to maintain in the long run for sites that
are more than several pages large. To put it simply, the source pages
are a mess, with VBSCript/JScript interspersed with HTML tags.
We had a guy who worked on a short project using ASP (using Visual
Interdev), and he was glad to be done with it when it was over. He said
it was easy to create, but it looked ugly and inelegent, and was going
to be hard to maintain in the long run (even though it was a relatively
small site).
Blake Buzzini wrote:
>
> I program for the PSU College of Engineering, which is an MS shop top to
> bottom. I'm going to be programming a very large, entirely dynamic
> server-side application which will need to do things like image processing
> and writing GIFs back to the client. My boss wants to use ASP. Any
> suggestions on how I can talk him into servlets? He just wrote me, after
> reading WebReview's excerpt of Jason's book, saying that servlets are just
> "Java's implementation of ASP", so we might as well use ASP. Oy.
>
> Thanks,
> Blake
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
