> Brian Zimbelman wrote:
>
> Guys,
>
> Why is it that people seem to want to make everything a servlet?
> [...]
> Just curious as to what I'm missing, as I tend to put everything
> that is not about handling requests from the user and building HTML
> responses in something other than the servlets (clean separation of
> the model and the view in my mind).
>
Hi,
I think it has to do with the deployment environment: I'm often
developing for servers that I don't have any control over - that is,
they're web-hosting accounts. And, typically running on a
network/multiuser-unfriendly OS like Windows NT.
So, the most I can count on is FTP access to my host. Deploying
server-side apps as servlets (and a ServletExec-like control panel)
gets around the problems this causes.
FWIW, I completely agree with you that not everything is a servlet. I
like to design things so that the server is actually a stand-alone
class with a clear interface. So that, for example, its services
could also be accessed through RMI.
I've been thinking about ways to start RMI servers remotely - perhaps
by first firing up a servlet; but that sounds like it'd get complex
and hard to manage.
- Robb
___________________________________________________________________________
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
