> But configuration should be a POJO - a class with setters and getters,
nothing else.
Why it should? Why ClientConfiguration should be serializable? Who needs
that? Xml configuration even in spring are not widely used for years :)
вс, 11 июл. 2021 г., 00:57 Pavel Tupitsyn :
> Ivan D,
>
> Let's
Ivan D,
Let's compare WebClient approach with Ignite 2.x approach:
// Ignite 2.x
var cfg = new ClientConfiguration()
.setAddresses("127.0.0.1:10800", "127.0.0.1:10801")
.setTimeout(4000);
Ignite client = Ignition.startClient(cfg);
// Ignite 3.x in
Pavel, I and Ivan P. have already get examples of lettuce.io
Another example is spring 5 reactive WebClient
https://www.baeldung.com/spring-5-webclient
сб, 10 июл. 2021 г., 19:50 Pavel Tupitsyn :
> Ivan D.,
>
> > simple and straightforward client builder
> Can you please provide an example of
Ivan D.,
> simple and straightforward client builder
Can you please provide an example of that, a piece of code with suggested
API usage? Ideally compared to the current 2.x approach.
On Sat, Jul 10, 2021 at 3:20 PM Ivan Daschinsky wrote:
> It is a quite questionable decision , as for me, to h
It is a quite questionable decision , as for me, to have specific static
method within strange class with strange name (and it is a well known
antipatter ) with chained twisted configuration class instead of just
simple and straightforward client builder, isn't it? Name 'Ignition' is may
be fun, b
Val,
My suggestion is to have Ignition class in ignite-client module.
On Fri, Jul 9, 2021 at 11:01 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Pavel,
>
> Ivan actually brings a good point. While the client is in a separate
> module, Ignition (if we make it static) will have
