Re: Merging all network components to a single one

2017-03-10 Thread Dmitriy Setrakyan
Agree with Denis. It is not practical to remove any existing SPIs unless we come up with proper TCP SPI design and implementation. I think it will be enough to simply deprecate the existing SPIs we plan to remove, without physically removing them, until the design is finalized. D. On Fri, Mar

Re: Merging all network components to a single one

2017-03-10 Thread Denis Magda
> Denis, I think we can allow this as well, but not as SPI since I want to > drop them and create 1 internal component to manage all interconnections. I > think this is enough since additions/changes will be rare and they will > result in changing internal code (including support of technologies

Re: Merging all network components to a single one

2017-03-10 Thread Yakov Zhdanov
Dmitry, you are right - this seems to be a very complex change. However, we can we move current implementations to internal packages, introduce configuration properties/beans so we can release and continue development in 2.0 without breaking compatibility. Denis, I think we can allow this as

Re: Merging all network components to a single one

2017-03-09 Thread Dmitriy Setrakyan
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

Re: Merging all network components to a single one

2017-03-09 Thread Denis Magda
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

Re: Merging all network components to a single one

2017-03-09 Thread Yakov Zhdanov
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,

Re: Merging all network components to a single one

2017-03-07 Thread Denis Magda
Personally, I’m fully for this idea. BTW, there is already a ticket for this task created by Yakov some time ago: https://issues.apache.org/jira/browse/IGNITE-3480 — Denis > On Mar 7, 2017, at 10:50 AM, Dmitriy Setrakyan

Re: Merging all network components to a single one

2017-03-07 Thread ALEKSEY KUZNETSOV
What tasks do discovery component responsible for ? вт, 7 мар. 2017 г. в 13:15, Yakov Zhdanov : > Guys, > > I have an idea of merging all net components to one. > > Now we have the following components interacting via network: > 1. discovery > 2. communication > 3. rest > 4.

Merging all network components to a single one

2017-03-07 Thread Yakov Zhdanov
Guys, I have an idea of merging all net components to one. Now we have the following components interacting via network: 1. discovery 2. communication 3. rest 4. odbc 5. ignite-hadoop 6. time processor (being removed together with clock mode) 7. IPC communication endpoint 2-6 use GridNioServer