Galder, I've been busy looking for a new job and thus a little
...
distracted. Anyway, you made a valid point I simply failed to recognize.
So this is my updated personal roadmap:
1. Make Spring Infinispan (I really should have chosen Infinispring)
reasonably for both the embedded as well as the remote use case.
It's not too late. ;)
2. Turn my attention to ISPN-984. I will probably need some guidance
to get up to speed.
You'd need help from Galder and Mircea on this, particularly around enhancing the wire
protocol.
Yes, I would love to improve my as of now rather theoretical Scala
skills, mostly gleaned from working through some tutorials. So expect to
give me some tips.
Cheers,
Olaf
Am 16.03.11 09:06, schrieb Galder ZamarreƱo:
> Olaf, you're current method won't work since it will only give you the cache
names of the caches being interacted with by that client. It does not represent all the
caches active on the server side.
>
> It's something that could be useful and easy to implement - I've created
https://issues.jboss.org/browse/ISPN-984
>
> Olaf, if you fancy learning some Scala, you could try implementing it when you're
finished with the Spring work? I can guide you through it :)
>
> On Mar 14, 2011, at 1:40 PM, Manik Surtani wrote:
>
>> There isn't anything of the sort at the moment. I presume you'd just
have to use a singleton list containing the default cache name for now.
>>
>> Galder/Mircea, what are your thoughts around adding a verb to retrieve cache
names to Hot Rod?
>>
>>
>> On 13 Mar 2011, at 22:30, Olaf Bergner wrote:
>>
>>> I have more or less finished my first attempt at implementing Spring
>>> 3.1's forthcoming cache abstraction for Infinispan embedded. While doing
>>> the same for Infinispan remote, i.e. for Infinispan's hotrod client, I
>>> noticed that org.infinispan.client.hotrod.RemoteCacheManager lacks a
>>> method for asking it for the names of all caches that are currently
>>> known to it. This, however, is required for successfully implementing
>>> org.springframework.cache.CacheManager. For now, I work around this
>>> limitation by using reflection to get at RemoteCacheManager's map from
>>> cache names to caches. Suffice it to say that this reeks of a hack.
>>>
>>> So do you think that adding such a method to RemoteCacheManager is
>>> feasible? Alternatively, do you know of any other way to get at the
>>> names of all caches managed by RemoteCacheManager?
>>>
>>> Cheers,
>>> Olaf
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> --
>> Manik Surtani
>> manik(a)jboss.org
>>
twitter.com/maniksurtani
>>
>> Lead, Infinispan
>>
http://www.infinispan.org
>>
>>
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
> --
> Galder ZamarreƱo
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev