On Monday, September 3, 2012 7:01:42 PM UTC+5:45, chadkouse wrote: > > Would it be possible to have your consumer remote control a different > server to process the job and remotely issue the reboot command? Then > polling the remote server to see when it comes back up? In other words the > consumer wouldn't actually do the work or reboot but would be responsible > for telling a 3rd party server what to do? > > This way you wouldn't lose the reference to the reserved job, however it > would add some complexity and additional components to your process. >
I think that would just leave me with the same level of complexity but at one remove. I went over the existing protocol again, and it seems like I can't do this with beanstalkd, which is extremely vexing. Even if I hacked in the delete command to delete jobs in other people's reserved queues, there's still every chance that the connection would error while the client was rebooting, and the job would then get released anyway. Bury would work, if you could bury with a timeout :/ Maybe I could use a new tube, one per client, and use that as a 'shelf' of sorts. Anyway, thanks for the ideas. Cheers, ben -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/2WPHI3nLvdEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
