On Wednesday, June 12, 2013 10:47:48 PM UTC+1, Keith Rarick wrote: > > > For our purposes, a change is compatible if we can > expect existing clients to continue to work as designed. > Oh that's great news to hear. I wasn't sure if that was the case, and looking at my pet features I'm sure that they could be developed to meet that requirement.
> Most of the outstanding features in the issue tracker > can comfortably be implemented in a compatible way, > including the two you listed. I'd love to see them go in. > Most of these features require some design work as > well as implementation. I'm happy to collaborate on > design issues, even though I haven't had time lately > to work on implementation for new beanstalkd features. > Again, that's music to my ears. I will definitely see if I can draft something that can help move these features forwards > > Most of my beanstalkd time in recent months has > been spent fixing important bugs as they arise. That, > along with some janitorial work in the code, continues > to be my priority. Fortunately, the rate of new bugs > being reported has been slowing down lately (even as > beanstalkd gets more popular). And I'm happy to merge > in new features even when I'm personally focused on > code cleanup and bug fixing. > That's a great tidbit of news on the stability of beanstalk. Bolsters my confidence with regards to beanstalk being the right choice for us. We use it for pretty much evry project (we're predominately a PHP dev team and we use beanstalk as a great way to circumvent the single threading issues of PHP) > > If you want to see a new feature go in, the most > effective first step is to propose a design for the feature > that's compatible with the current protocol. It can happen > here on the mailing list or on the issue tracker; the > mailing list will reach a wider audience. These designs > usually take the form of draft changes to the protocol > spec and some examples of use. Once we agree on a > design, it's much easier for someone to come along > and implement it. (And if you want to go ahead and > implement it yourself, so much the better!) > > Yup, will definitely start work on those protocol designs. Unfortunately I'm not a C developer but I can at least help get the ball rolling. Thanks for the detailed response! -- 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.
