[JBoss JIRA] Created: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
10:46 p.m.
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: Manik Surtani
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
10:46 p.m.
New subject: [JBoss JIRA] Assigned: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ http://jira.jboss.com/jira/browse/JBCACHE-880?page=all ]
Elias Ross reassigned JBCACHE-880:
----------------------------------
Assignee: Elias Ross (was: Manik Surtani)
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
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
8:37 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ http://jira.jboss.com/jira/browse/JBCACHE-880?page=comments#action_12349636 ]
Manik Surtani commented on JBCACHE-880:
---------------------------------------
Could you pls link to the discussion thread in this task. Also add that this will require
documentation and configuration changes.
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
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
8:45 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ http://jira.jboss.com/jira/browse/JBCACHE-880?page=comments#action_12349640 ]
Manik Surtani commented on JBCACHE-880:
---------------------------------------
Marking as a known failure in build.xml (ExpirationPolicyTest fails intermittently on
HEAD) for 2.0.0.ALPHA2.
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
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
11:34 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ http://jira.jboss.com/jira/browse/JBCACHE-880?page=all ]
Elias Ross updated JBCACHE-880:
-------------------------------
Description:
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", ... );
was:
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", ... );
Affects: [Documentation (Ref Guide, User Guide, etc.)]
Added documentation and sample configuration.
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
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
11:37 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ http://jira.jboss.com/jira/browse/JBCACHE-880?page=all ]
Elias Ross updated JBCACHE-880:
-------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=95750
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
11:37 p.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
[ 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
6493
days inactive
6537
days old
6 comments
2 participants
participants (2)
-
Elias Ross (JIRA) -
Manik Surtani (JIRA)