Venkatesh,
It has been my experience that a full-fledged application server usually
handles nearly all aspects of a particular applications lifetime, from
development to testing and finally to production. In general an application
server handles page serving, serlvet/program execution, and backend resource
management. An application server, IMHO, places all of your eggs in one
basket, and as such, marries you to a particular vendor. Which as many of
us know, isn't always a good thing.
A servlet engine really only handles one thing, loading, instantiating and
executing a given servlet. In some cases, the line between and servlet
engine and an application server becomes very blurry. I believe the JRun
lands somewhere in the middle. Only because it can serve HTML pages,
servlets, and provides connectivity between a full-fledged web server and
the servlet engine.
At any rate, it seems deciding on one application server generally entails
an initial outlay of a lot of cash as they don't come cheap.
I welcome any comments on this subject.
Brian
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
> Venkatesh Kumar A G
> Sent: Sunday, May 16, 1999 11:36 PM
> To: [EMAIL PROTECTED]
> Subject: Appserver and Servlet Engine
>
>
> Dear All,
> Can anyone highlight what is the difference between Application
> server and
> a Servlet Engine Server.
>
> Thanks
> Venkatesh
>
___________________________________________________________________________
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
