I see. Thanks. The thing is, to make such a thing useful over a non persistent connection would require some changes. I could probably implement it in a custom way but it will require some backend and a set of threads to run and do some periodic cleanup and changes.
The choice of reasonable backends is rather limited, Redis being the one obvious choice (as opposed to an RDBMS or other such things). Is there a document describing a bit what internal data structures beanstalkd uses and what type of threads do the various jobs of moving items between states? If not I'll just have to dive into the code :-) Thanks for writing and sharing beanstalkd and for the response :-) Eran On Monday, October 31, 2011 at 1:58 AM, Keith Rarick wrote: > Sorry, beanstalkd doesn't work that way. > I'd be interested in seeing any patches you > make, and I'm happy to answer questions > about beanstalkd's internals and to provide > guidance on working with the code, but it's > unlikely that I'll pull them. > > kr > > -- > 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] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/beanstalk-talk?hl=en. > > -- 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.
