4:06 p.m.
Hi,
After we resolve streaming format incompatible cacheloader
implementations [1][2], and as we continue to follow newly agreed
streaming state transfer format - we do not have to require cacheloader
implementers to write their own implementations of storeEntireState and
storeState !
CacheLoader.storeEntireState and CacheLoader.storeState are always the
same. They read NodeData objects from stream and call put with
underlying cacheloader. Put method does the cacheloader specific stuff.
We can possibly keep storeEntireState and storeState in CacheLoader API
but move default implementations to AbstractCacheLoader. Any suggestions
or opinions?
[1] http://jira.jboss.com/jira/browse/JBCACHE-748
[2] http://jira.jboss.com/jira/browse/JBCACHE-749
4:46 p.m.
Absolutely, I had that idea when I wrote the cache loader interface, but
never saw it through... +1 for sure, this takes a lot of pain out of the
implementations.
Are you guys thinking about a more efficient transfer format, or is
NodeData still the awy to go ?
Vladimir Blagojevic wrote:
Hi,
After we resolve streaming format incompatible cacheloader
implementations [1][2], and as we continue to follow newly agreed
streaming state transfer format - we do not have to require cacheloader
implementers to write their own implementations of storeEntireState and
storeState !
CacheLoader.storeEntireState and CacheLoader.storeState are always the
same. They read NodeData objects from stream and call put with
underlying cacheloader. Put method does the cacheloader specific stuff.
We can possibly keep storeEntireState and storeState in CacheLoader API
but move default implementations to AbstractCacheLoader. Any suggestions
or opinions?
[1] http://jira.jboss.com/jira/browse/JBCACHE-748
[2] http://jira.jboss.com/jira/browse/JBCACHE-749
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
--
Bela Ban
Lead JGroups / Manager JBoss Clustering Group
JBoss - a division of Red Hat
4:21 a.m.
Yes, this sounds like a good idea. If implementors want to fine tune
the way they handle these methods they can override them.
+1.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 31 Aug 2006, at 22:06, Vladimir Blagojevic wrote:
Hi,
After we resolve streaming format incompatible cacheloader
implementations [1][2], and as we continue to follow newly agreed
streaming state transfer format - we do not have to require
cacheloader
implementers to write their own implementations of storeEntireState
and
storeState !
CacheLoader.storeEntireState and CacheLoader.storeState are always the
same. They read NodeData objects from stream and call put with
underlying cacheloader. Put method does the cacheloader specific
stuff.
We can possibly keep storeEntireState and storeState in CacheLoader
API
but move default implementations to AbstractCacheLoader. Any
suggestions
or opinions?
[1] http://jira.jboss.com/jira/browse/JBCACHE-748
[2] http://jira.jboss.com/jira/browse/JBCACHE-749
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
6657
days inactive
6658
days old
jbosscache-dev@lists.jboss.org
2 comments
3 participants
participants (3)
-
Bela Ban -
Manik Surtani -
Vladimir Blagojevic