[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys

[Elias Ross (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-841?page=comments#action_12417667 ] 
            
Elias Ross commented on JBCACHE-841:
------------------------------------

The initial use case was supporting such collections as SortedMap in POJO cache. SortedMap implementations typically allow for ordering to be done in two ways: By using natural ordering of the elements, e.g. Strings ordered lowercase first; or through a Comparator instance. Although I'm thinking that this "setting" could be transient (not persisted or replicated), for POJO Cache it probably needs to be stored someplace. POJO Cache can probably take care of setting it in a related Node.

But in general, users would naturally expect the Node ordering property to be made persistent and replicated. I'm thinking that JBoss Cache would need a separate data map that's for meta-data like this.

Initially, it might be easiest to simply have ordering defined by Region and only support natural ordering.

> 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