Brian Zimbelman wrote:
>
>
> Guys,
>
> Why is it that people seem to want to make everything a servlet? What
> about this cron class is servlet like? Is it getting invoked by a http
> request? When I wrote our cron-like utility (very basic replacement
> that handles what we need, doesn't have all the bells and whistles of
> cron, runs on all platforms, controlled via our database not crontab
> files) I wrote it as a Java application.
>
> 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).
>
> Thanks,
> Brian
>
I agree with Brian. Instead of "a servlet to run background cron jobs",
I would rather see "a background job runner that can be administered
with servlets". The difference is subtle, but important -- not every
application in the world needs to be a servlet itself.
Craig McClanahan
___________________________________________________________________________
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
