ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@gridgain.com>
Subject Re: Idiomatic way of configuring caches on client
Date Wed, 09 Dec 2015 14:07:16 GMT
Alex,

Thanks for your suggestions. We will generate server cache configs + client
near cache configs.

On Wed, Dec 9, 2015 at 9:06 PM, Alexey Kuznetsov <akuznetsov@gridgain.com>
wrote:

> Yakov, Ignite console has UI (on Summary page) for near cache
> configuration with optional eviction policy.
>
> On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov <yzhdanov@apache.org> wrote:
>
>> I think it is very good idea to generate client node config as well and it
>> seems that console should provide ability to configure near cache (e.g.
>> start size and eviction policy) or turn it off completely.
>>
>> --Yakov
>>
>> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov <akuznetsov@gridgain.com>:
>>
>> > I'm working on Ignite Web Console.
>> > And this utility is generating XML and java code with cluster
>> > configuration.
>> >
>> > For server-side I generate XML and java code that describe caches.
>> >
>> > But should I do the same when generating client node configuration?
>> >
>> > I think that I should only generate NearCacheConfiguration in case
>> > of client node
>> > and do not generate CacheConfiguration in XML and java.
>> >
>> > Also, it is a good idea to generate NearCacheConfiguration for each
>> cache
>> > by default?
>> > Or better to give a choice of caches?
>> >
>> >
>> > Thoughts?
>> >
>> > --
>> > Alexey Kuznetsov
>> > GridGain Systems
>> > www.gridgain.com
>> >
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

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