cron functionality for noosfero

[Aurélio A. Heckert]

Hi Hugo,

The DelayedJob is an option to you, but that is not a nice one.
Rodrigo used this way only because he has no time to do a better solution.

Using the DelayedJob you must schedule a new task in a previews task.
If you get an error (in your task or in DelayedJob) you will lost the new
task schedule.
Game Over.

In javascript:

   - DelayedJob = setTimeout = one time problems = repeat extra code =
   repeat risk
   - Cron like = setInterval = repeat forever = no repeat code = repeat
   haven

I believe you get it. ;-)

A cron like approach will be better. To your work and also to spaminator.
The new version DelayedJob https://github.com/collectiveidea/delayed_job **
may** help, but i'm not sure.

There is an old cast about it:
http://railscasts.com/episodes/164-cron-in-ruby

Another nice approach may be add a noosfero script to /etc/cron.d to poke
noosfero's CronJob.runSchedule(now) using ./script/runner.
The nice thing is: No new daemon. If a task die, the system will run cron
again, like nothing happens.

Hasta!

-- 
Aurélio A. Heckert  http://SoftwareLivre.org/aurium
Coop. de Tecnologias Livres: http://Colivre.coop.br
     - - - - - - - - - - - - - - - - - - - - - - - - -
GNU/Linux User #312507  http://counter.li.org
Ilustração Vetorial Livre: http://InkscapeBrasil.org
     - - - - - - - - - - - - - - - - - - - - - - - - -
  "Windows 7: a new era of restrictions."
   http://windows7sins.org

   Antes de imprimir esta mensagem reflita
   sobre a sua responsabilidade com a
   preservação do Meio Ambiente.
-------------- Pr?xima Parte ----------
Um anexo em HTML foi limpo...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20130227/0a385057/attachment.html>