On Fri, Jan 22, 2021 at 11:19 PM Александр Рябов <[email protected]> wrote: > I found a bug. When producer adds a new job when consumer is running > in parallel, beanstalk gives newly added job to consumer and returns reply > to producer only after sent job to consumer.
The protocol spec and the documentation for beanstalkd do not specify an order in which these events must occur. The implementation is free to choose. So I would say the observed behavior conforms to the spec. In general, it is good for specifications not to overly constrain the software that implements them. They should specify only what they need to, and otherwise leave implementations (such as beanstalkd) free to choose an approach that suits them and satisfies other constraints they may be facing. That said, if you think it would be useful for the specification to determine this ordering, we should weigh the trade-off of that on the one hand vs letting the implementation retain more flexibility on the other hand. Maybe we should update the spec. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beanstalk-talk/CAD25zGBqARN8_ao%2Bwyz8cxa3_satjtHcJbNweFbC5mT9AW%2BhUg%40mail.gmail.com.
