On Jan 7, 2011, at 9:19 PM, Ken Wesson wrote: > On the other hand, running a job scheduler from outside Clojure > results in cranking up a big, slow to start up, expensive JVM process > every single time a task needs to run, each of which runs one task > once, and the scheduling itself must be done in an icky language like > shell or cron's idiosyncratic "crontab" files with icky error > reporting (e.g., need to run a local mail *server* to receive error > notifications).
If you care about startup times, you can use nailgun. But that shouldn't matter unless you're running the job every minute or something. As for scheduling, crontabs are really not hard to figure out. If you need more complex scheduling, you can do that from your Clojure script (essentially using cron to set the polling interval). And what kinds of error reporting could you do from a persistent daemon that you couldn't also do from a cron job? Besides, most systems that have cron also come with postfix (though it's disabled by default on Mac OS X), so all you have to do is add your email address to /etc/aliases. Email-based error reporting for background tasks is really nice because you don't have to remember to check some log file or other task-specific status indicator periodically (which has burned me in the past). But this is all somewhat beside the point. What Trevor said sounded as though the specific types of tasks he mentioned (sending emails and checking some kind of status via web app) were particularly unsuited to scheduled jobs; I was asking what it was about those tasks in particular that made him lean towards a daemon instead. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
