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.
