On Dec 8, 2005, at 3:19 PM, Patrick Casey wrote:
Honestly, I looked into it and couldn't figure out what all the fuss
is about. For a little toy crud application it's nice and fast,
but, hey,
so's python, perl, or PHP.
It just doesn't have to features I'd need to build what I consider a
"real" application. One question in the rails forum kind of told me
everything I needed to know.
"So, how would I use rails to run a specific task on a repeating
schedule".
"What, like a scheduler?"
"Yes, exactly like a scheduler. I need to scavenge flagged deletes
in the background so that foreground performance doesn't have to
suffer."
"Well, umm, you could write a cron job ..."
I was deleting Rails off my machine within the hour. There were
other issues as well, but some of them at least seem to have been
resolved
since then (the n+1 selects problem has been solved for example).
I actually find the cron job separation quite clean and reasonable.
Die hard Java developers get stuck in the rut of thinking every
solution must run within a JVM. The operating system has a built-in
facility to run jobs, so it seems foolish to dismiss it and only seek
solutions that fit within the confines of a JVM.
I want a nightly job to rebuild some caches, nothing wrong with cron
running it.
RoR has a very nice "script/runner" facility to run code within a
selected environment (production, test, development, or custom ones
you create). Firing up a cron job to do a task is as easy as coding
the task, which for cache rebuilding may only be 5 lines or less, and
then adding one entry to the cron jobs. You can't touch that level
of cleanliness, succinctness, or productiveness with *any* Java
scheduling solution.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
