As far as I can tell the only benefit to storing the using and watching state per socket vs. including the tube(s) in every put and reserve command is if you intend on watching a long list of tubes. Otherwise specifying the tube to put a job into or the tubes to reserve per command seem cheap and much more convenient than executing separate use and watch commands.
To this end I've begun implementing stateless put and reserve commands: put-in-tube, reserve-tubes, and reserve-tubes-with-timeout. So far only put-in-tube is implemented. https://github.com/schmichael/beanstalkd/tree/stateless-commands I haven't updated the protocol docs or tests yet as I just quickly hacked this together in a couple hours this evening without ever having looked at beanstalkd's source before. Any feedback is welcome! -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
