> Does one want their http server to be managing the
> servlet, etc? Does one
> just want to execute some java code?
>
> Or... does one want an application server which is
> managing the caching of
> your objects, database pooling, multi-languages, etc?
>
> That's the real difference going with just a single fire
> off mechanism for
> a servlet versus an application server.
>
> The differences are vast and is a serious issue for a
> large scale site.
Well, then scale up to a servlet engine such as IBM WebSphere. It
supports servlets, Java Server Pages, load balancing, state
management, database pooling, front-end caching, Corba, etc etc
etc... It's still the same API, though.
