Thanks Keith, I was actually looking at the code to see if there is a way to add that feature in easily, but looks like because the connection goes into STATE_WAIT state when receives the RESERVE command, I need to change how states are managed to get the functionality that I want... so that's not an option any more :)
Closing the old connection and re-opening it might get too expensive for us, as this situation is a common thing in our application. One other solution is to create a new connection for the new tube and reserve on that, but this way we'll hit the system's connection limit very fast. Do you know if there is any way to get around that limit? -Payam -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/MwPMVyEnUcwJ. 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.
