On Mon, Jul 22, 2013 at 12:31 AM, Constantin Teodorescu <[email protected]> wrote: > That was forcing me to do some extra work of sending also the <job server > time> information and if the worker found that the job is "too old", it just > silently delete him!
This is the right approach. Have the worker do it. :) My general philosophy is to avoid adding anything to beanstalkd that clients can do already. And to make anything we do add useful in as many situations as possible (by making new things orthogonal and simple). > But that means that the two machines, the producer and worker should be > exactly time synchronized! :-( You can use the "age" field in stats-job to know how long the job has been in the server. This number is in seconds; if that's not fine-grained enough, we should maybe extend its precision. I'm glad you find beanstalkd useful! -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/groups/opt_out.
