Sounds good to me, we should have a little more breathing room after the NBST alpha to look at the state transfer integration.<br><br>Cheers<br>Dan<br><br><br><div class="gmail_quote">On Tue, Jul 24, 2012 at 6:08 PM, Mircea Markus <span dir="ltr">&lt;<a href="mailto:mircea.markus@jboss.com" target="_blank">mircea.markus@jboss.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi guys,<div><br></div><div>I&#39;ve just had a chat with the CloudTM team(CC) around the integration of TOB/TOA[1] into Infinispan. Here are some points:</div>
<div>- the TOB and TOA code has been reviewed in detail by us. The only part missing is the state transfer integration</div><div>- there&#39;s not a lot of sense in integrating TOB/TOM over the existing state transfer as we would not back port that to 5.1 and it would be dropped in 5.2</div>
<div>- CloudTM would rebase the TOB/TOA work on top of the alpha NBST[2](ATM planned at the end of  next week/3 Aug) and we&#39;ll integrate that </div><div>- first releases of the TOB/TOA would be marked as experimental in 5.2  </div>
<div><br></div><div>How does that sound?</div><div><br></div><div>Cheers,</div><div>Mircea</div><div><br></div><div>[1] TOA used to be referred to as TOM (M from multicast). In JGroups terminology that&#39;s an Anycast, so we decided to be consistent with that and use TOAnycast.</div>
<div>[2] <a href="https://community.jboss.org/wiki/Non-blockingStateTransfer" target="_blank">https://community.jboss.org/wiki/Non-blockingStateTransfer</a></div></div><br>_______________________________________________<br>

infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br></blockquote></div><br>