ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: supporting different configuration format json,yaml...
Date Tue, 15 May 2018 06:31:26 GMT
Dmitriy,

We don't need to support different config formats on server in order to add
that to thin clients.

Thin client protocol provides a way to create a cache with custom config
[1].
It is up to thin client library authors to use any config format they like
and then convert it into protocol-defined format.

C# thin client uses custom format, for example, not Spring.

[1]
https://apacheignite.readme.io/docs/binary-client-protocol-cache-configuration-operations#section-op_cache_create_with_configuration

On Mon, May 14, 2018 at 7:54 PM, Ivan Rakov <ivan.glukos@gmail.com> wrote:

> Dmitry,
>
> We rely on Spring Framework when we start Ignite node from XML
> configuration. Spring doesn't easily support another formats of
> configuration files. I think, the main reason for this is built-in ability
> to validate configuration via XML Schema. We can surely hack this around (I
> bet there are existing libraries for configuring Spring with JSON), but I
> don't think that anyone suffered from inability to statically configure
> Ignite with json/yaml.
>
> Regarding thin clients: makes sense. I suppose necessary mappings will be
> implemented as a part of thin client.
>
> Best Regards,
> Ivan Rakov
>
>
> On 14.05.2018 18:58, Dmitriy Govorukhin wrote:
>
>> Hi, Igniters!
>>
>> As far as I know, many people work on a thin client for different language
>> (go,js,php...).
>> Are there any reasons why ignite does not support yaml or json format for
>> configuration? or some other popular format?
>> In future, it can help to integrate with thin clients, for example, js
>> client may want to dynamic cache start, he passes cache configuration (in
>> native format, for js it will json) through TCP, Ignite node unwrap and
>> remap to java representation and dynamic start cache.
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message