So: using one shared connection across all threads would be simpler, but TrendrrBeanstalk might be more high-performing for high-volume situations. Is that right?
Dan On Tuesday, November 16, 2010 6:06:13 PM UTC-6, Robert wrote:Hi Dan, 1. If you use, Client.setUniqueConnectionPerThread(false); you'll get one shared connection across all threads. 2. The default behavior continues to be one connection per thread. If you're interested in pooling, check out TrendrrBeanstalk, which was announced yesterday. I haven't pulled it down yet, but it does support client pooling. -- 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.
