On 30 Jul 2009, at 18:04, Clebert Suconic wrote:
yes.. .the Journal is not a DB.
You have method to recover the state on load. but you need to keep the
data yourself outside of the Journal on the HashMaps.
The Journal is a way to make your memory persistent.
I thought this was the case for Infinispan. Maybe I missed something
when reading the code.
Yes - the cache store stores a superset of what is in memory.
Overflow. So it still needs to be accessible in a random fashion,
using a key.
See the load() API on the CacheLoader interface.
On 07/30/2009 12:00 PM, Jason T. Greene wrote:
> Last time this was discussed, it was mentioned that the journal does
> not provide random access. Is this still the case? In order for a
> cache store/loader to be useful, it needs to offer an indexing
> mechanism.
>
> Clebert Suconic wrote:
>> I had a quick look on the Persistence code for Infinispan yesterday,
>> and it looks like the JBoss Messaging Journal was just made for
>> infinispan.
>>
>>
>> The only thing I couldn' t understand was the streaming operations
>> fromStream and toStream. What they are used for, and how they
>> translate into multiple records?
>>
>>
>> We have talked about making the Journal a sub project of JBoss
>> Messaging, in a way other projects would be able to reuse (if that
>> interests you guys).
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Clebert
>> _______________________________________________
>> 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
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org