Hi I have been playing with adding a new set of features to beanstalkd and wanted to know if there were anyone else is interested (so that I can finish the code and tidy it up).
A bit of history: I updating an application that processes inbound emails from customers. These need to be processed in order of arrival and are handled by a web application. I already use beanstalkd for other components of the system (and it works really well ;-) ) so wanted to replace the database based queue with beanstalkd. The issue (obviously) is that each request that initiates the connection to the server, reserves a job and then closes the connection - instantly releasing the job. So I have added a new command to the grammar of the protocol. "preserve". This is only valid after a a job is reserved (in the same way as "bury" works - however the preservation is only valid until the existing reservation. It releases in the same way as a normal reservation (i.e. when the expiry time is reached or if the server is restarted and binary logging is enabled) but not if the connection is dropped. I have got this most of this working now so wanted to know how interested people were. cheers Matt -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. 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.
