To my understanding, Yakov is suggesting that we simply have one very low level SPI - let's call it IgniteTcpSpi and current implementations of discovery and communication will be removed from SPI layer and will register callbacks with this new SPI.
I think this is too big of a change to try to squeeze it into 2.0 release. Yakov, what are your thoughts. On Thu, Mar 9, 2017 at 10:30 AM, Denis Magda <dma...@apache.org> wrote: > Yakov, > > However an end user still will be able to provide its own implementation > for this combiner discovery & communication layers, right? > Just want to be sure that if I want to add some custom RDMA, RoCe or > InfiniBand implementation then I’ll be able to do this. > > — > Denis > > > On Mar 9, 2017, at 1:11 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > > > > Dmitry, yes, your understanding is correct. > > > > Denis, I remember I already shared the idea a while ago, but completely > > forgot about the ticket. Thanks for bringing it up! You should give me > > couple of tips on how to use "Search" function in Jira :) > > > > Guys, this will be compatibility breaking change, as there will be no, > for > > example, discovery and communication SPIs. What if we move current > > implementations to internal packages, introduce configuration > > properties/beans so we can release and continue development in 2.0 > without > > breaking compatibility? > > > > --Yakov > >
