[
http://jira.jboss.com/jira/browse/JBCACHE-1134?page=comments#action_12368758 ]
Galder Zamarreno commented on JBCACHE-1134:
-------------------------------------------
The difference between the classes extending
DelegatingCacheLoader and the classes extending
AbstractDelegatingCacheLoader is:
Classes extending DelegatingCacheLoader are
standalone classloaders, whereas the ones extending
AbstractDelegatingCacheLoader are decorators of other
class loaders.
Maybe decorators, such as asynchronous or singleton
store could one day become standalone cache loaders and
stack/chaim them up/down other standard cache loaders?
I'll open a discussion in the design forums soon.
Consolidate delegating cache loader classes
-------------------------------------------
Key: JBCACHE-1134
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1134
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.1.SP3, 2.0.0.CR3
Reporter: Galder Zamarreno
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.CR4, 2.0.0.GA
In the org.jboss.cache.loader package, we have:
o.j.c.l.DelegatingCacheLoader and
o.j.c.l.AbstractDelegatingCacheLoader
The second one was created by me when I first created
SingletonStoreCL (doh!). I refactored common code
from AsyncCL to AbstractDelegatingCL and made
AsyncCL and SingletonStoreCL.
I have just spotted DelegatingCacheLoader which is
extended by LocalDelegatingCacheLoader and
TcpDelegatingCacheLoader.
We should try to consolidate, if possible, all delegating
cache loaders into one DelegatingCacheLoader interface
and an abstract implementation.
It'd be nice if this could be done by 2.0.GA, so setting that
fix version for the moment :). Otherwise, we'll have to leave it
for 3.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira