A lot of people have been asking about this. I think SASL support is worthwhile.
Right now, I plan on having no fancy authorization, per-tube access, or anything like that, just a binary connect-or-not decision. This is sufficient for the most common case, where a user wants to run beanstalkd in a shared network and trusts the network administrators but not the other users of the network. This is the situation in EC2, for example, or so I have been led to believe. It also adds no overhead once the connection has been established. Are there other scenarios where this is not adequate? How many people want to deploy beanstalkd in those other scenarios? 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]. 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.
