[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key

[Elias Ross (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-880?page=all ]

Elias Ross resolved JBCACHE-880.
--------------------------------

    Fix Version/s: 2.0.0.ALPHA2
       Resolution: Done

Unit test should be more robust now.

> Add expiration policy for nodes based on a node's expiration key
> ----------------------------------------------------------------
>
>                 Key: JBCACHE-880
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-880
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Elias Ross
>         Assigned To: Elias Ross
>             Fix For: 2.0.0.ALPHA2
>
>
> It is useful to specify an expiration time (TTL) for cache values individually. For example, in caching web page contents, the data should be retained based on the HTTP header "Expires". Or, for caching session data, it should be kept based on the user's preference, e.g. Yahoo! Mail allows the authentication credentials to be cached from 1-24 hours.
> Example usage:
> TreeCache cache;
> Fqn fqn1 = new Fqn("node1");
> Fqn fqn2 = new Fqn("node2");
> cache.put(fqn1, "expiration", new Long( ... ));
> cache.put(fqn1, "data", ... );
> cache.put(fqn2, "expiration", new Long( ... ));
> cache.put(fqn2, "data", ... );

-- 
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