Quizas sea mas sensato usar setTimeout al finalizar en lugar de setInterval (lo digo de cabeza... Creo recordar que estaba asi)

Enviado desde mi iPhone

El 24/10/2013, a las 10:10, "Aitor Magán García" <notifications@github.com<mailto:notifications@github.com>> escribió:


In lib/retryBuckets.js:

> +local task=ARGV[1]\n\
> +local id_consumer=KEYS[1]\n\
> +local bucket=KEYS[2]\n\
> +redis.call('del', id_consumer)\n\
> +return redis.call('rpush', bucket, task)\n\
> +";*/
> +
> +/**
> + *
> + * @param task The task to be pushed on the bucket
> + * @param error Error that arises when the task was being processed
> + * @param maxRetry Max number of times that the task can be retried (each worker can define this with different values
> + * and this module is worker independent). If this value is not present, task will be pushed on the bucket.
> + * @param callback Callback to be called on error or success
> + */
> +exports.insertOnBucket = function (task, error, maxRetry, callback) {


Not now, but it could be useful in the future if you introduce a new event worker.

—
Reply to this email directly or view it on GitHub<https://github.com/telefonicaid/Rush/pull/200/files#r7181684>.

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx