FW: Using servlets for periodic background processes

[Michael Nash]

Title: RE: Using servlets for periodic background processes

 

Brian:

 

It's a very valid point: The only reason the scheduler process I wrote has anything to do with servlets is that it is administered via servlets - it is not itself a servlet, just a threaded object that can be invoked by a servlet or directly from the server system in a seperate VM.  MVC tehnique definitely indicates that the UI for administration of a scheduler/cron utility should be quite seperate from the processing itself.

 

I don't think you're missing anything!

 

Mike

http://www.javacorporate.com

-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Zimbelman
Sent: Saturday, August 21, 1999 8:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Using servlets for periodic background processes

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