[jboss-jira] [JBoss JIRA] Created: (JBCACHE-801) When we moved to EvictionInterceptor from a TreeCacheListener-based approach, one thing we lost is the ability for custom policies to prevent certain kinds of events going into the eviction queue. For example, a customer wants to prevent node modification

[Brian Stansberry (JIRA)]

When we moved to EvictionInterceptor from a TreeCacheListener-based approach, one thing we lost is the ability for custom policies to prevent certain kinds of events going into the eviction queue. For example, a customer wants to prevent node modification
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBCACHE-801
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-801
             Project: JBoss Cache
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 1.4.0.SP1, 1.4.0, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: 2.0.0


When we moved to EvictionInterceptor from a TreeCacheListener-based approach, one thing we lost is the ability for custom policies to prevent certain kinds of events going into the eviction queue. For example, a customer wants to prevent node modifications and visits from going in the queue as they are far too numerous for his app; he just wants adds (and maybe removes) so he can evict solely based on maxNodeAge.

Currently the only hook we provide to prevent an event going into the queue is EvictionPolicy.canIgnoreEvent(Fqn). But, when this call is made, we know the event type and even have a bunch of int constants identifying the valid types. So, we will 1) create a proper JDK5 Enum of the event types, and 2) change the EvictionPolicy interface to:

boolean canIgnoreEvent(Fqn fqn, NodeEventType eventType)	

The existing policies would just ignore the second parameter.

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