Alex, Ivan,
Good point about GridNioServer, I'll give it a try.
> java thin client (and other thin clients) should be
> separated from the main ignite repo
This is a big and complex topic, I'd prefer to avoid it here,
please start a separate thread.
On Mon, Oct 19, 2020 at 12:50 PM Ilya
>> Why can't we use GridNioServer for java thin clients?
Yes, we can. Despite the naming, it can be used as client (set port as -1),
But doesn't have the same set of advantages as Netty. Netty has a way
better support (performance) for native transports and SSL, that
default java NIO.
But API is
Hi.
>> Potentially reduced resource usage - share EventLoopGroop across all
connections within one IgniteClient.
Not potentially, definitely. Current approach (one receiver thread per
TcpClientChannel and shared FJP for continuation) requires too many threads.
When TcpClientChannel is the only
Igniters,
I'm working on IEP-51 [1] to make Java thin client truly async
and make sure user threads are never blocked
(right now socket writes are performed from user threads).
I've investigated potential approaches and came to the conclusion
that Netty [2] is our best bet.
- Nice Future-based
