I'm interested in taking a crack at implementing SASL authentication. There is an existing ticket here:
https://github.com/kr/beanstalkd/issues/41 On this ticket, kr, you say: > This could be done by a generic SASL wrapper tool that > accepts connections, performs authentication, then transfers > the open file descriptor to beanstalkd with sendmsg. Is it your preference to have a standalone SASL authenticator rather than building the functionality directly into Beanstalk? One feature of this approach, I suppose, is that you could handle multiple users that don't trust one another from a single endpoint by dispatching to multiple beanstalkd instances. Jon -- 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.
