[
http://jira.jboss.com/jira/browse/JBCACHE-841?page=comments#action_12417670 ]
Manik Surtani commented on JBCACHE-841:
---------------------------------------
Good point about making this replicated/persisted. We already encode some information
this way; a generic way to do this for all such flags would be good. A MetaData object,
for example, that could be encoded in the node's data map under an internal key or
something like that.
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL:
http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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