FYI, added to Nexus. This completes the implementation of message batching in all protocols, and contains the complete Async Invocation API as well. Once we have an implementation of async request handling in Infinispan, which runs independent transactions in separate threads from an internal thread pool, I expect a significant performance increase ! -- Bela Ban, JGroups lead (http://www.jgroups.org) _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Thx, I'm afraid I don't know which components are going to be included in EAP 6.1; ask the EAP folks. On 2/28/13 1:14 PM, Sanne Grinovero wrote: > Very nice, thanks Bela! > > I'm wondering if I should upgrade the next crop of Search technology > to use it. In other words, do you expect the 3.3 line to be included > in EAP 6.1 ? > Otherwise I'm stuck on older version. > > Sanne > > On 28 February 2013 11:58, Bela Ban <bban(a)redhat.com&gt; wrote: >> FYI, >> >> added to Nexus. >> >> This completes the implementation of message batching in all protocols, >> and contains the complete Async Invocation API as well. Once we have an >> implementation of async request handling in Infinispan, which runs >> independent transactions in separate threads from an internal thread >> pool, I expect a significant performance increase !