Re: Introduce generic server configuration.

Ok, so here is the summary of proposed design: 1) We introduce org.apache.ignite.configuration.TcpEndpointConfiguration. This is generic bean which could be used in different components having TCP server semantics. 2) This class will contain a set of TCP-specific properties: class

Re: Introduce generic server configuration.

How about TcpEndpointConfiguration? --Yakov 2016-04-13 13:22 GMT+03:00 Vladimir Ozerov : > Yakov, > > I thought about the following design: > > 1) Create org.apache.ignite.server.ServerConfiguration bean. I am not sure > about "server" word here, because it is too generic.

Re: Introduce generic server configuration.

Yakov, I thought about the following design: 1) Create org.apache.ignite.server.ServerConfiguration bean. I am not sure about "server" word here, because it is too generic. May be "endpoint" or "tcpServer", or something like this. 2) Then we plug this bean into other beans. E.g., for ODBC it

Re: Introduce generic server configuration.

Vladimir, I like the idea and it should really make things simpler, however, it is not clear to me how to incorporate this bean properly. NIO server is in internal package, but configuration should be under public one. Having this bean on public API of components exposes their internal

Re: Introduce generic server configuration.

+1 for such a bean. -Roman On Monday, April 11, 2016 11:48 PM, Vladimir Ozerov wrote: Igniters, We have several public components which use *GridNioServer* internally. NIO server has several properties for fine tuning. Selector count, direct buffer flag, max