On 13 Aug 2013, at 15:30, Galder Zamarreño <galder(a)redhat.com> wrote:
On Aug 13, 2013, at 12:20 PM, Mircea Markus
<mmarkus(a)redhat.com> wrote:
> On 13 Aug 2013, at 07:59, Galder Zamarreño <galder(a)redhat.com> wrote:
>
>> My preference is for #1.
>>
>> The main reason is cos JSR-107 is about to hit mainstream and we should try to
align with it in a way that we reduce confusion. Remember that JSR-107 users are potential
Infinispan users, and viceversa, so keeping these interfaces separated would make the
mental effort required to bridge the knowledge between the two easier.
>>
>> I tried to go back in the JSR-107 discussions to find discussions (google group)
on this topic but couldn't find anything. Maybe Manik remembers something about it,
but seems like this topic has been pretty much set in stone for quite a while.
>>
>> In terms of configuration, there's no issue at all. Each cache store provides
its own schema now.
>
>
> good point. Not the custom ones though, these still need a custom tag.
^ No, we don't, or if we currently do, we shouldn't stop doing so.
Nooo... writing a custom parser for a custom cache store is quite a bit of work and
requires understanding of ISPN configuration hierarchy. People would hate us! E.g. the
jdbc one:
http://goo.gl/VQiQ3u
IOW, even those who want to create a custom cache store should follow the same pattern of
providing their own XML schema parser for their config, configuration builder files…etc.
That gets rid of the problem altogether, and by checking the type of the cache
loader/store, we can figure out whether it's read-only, write-only or read-write
(assuming we keep the interfaces separated).
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)