Re: [infinispan-dev] org.infinispan.notifications.cachelistener.filter vs org.infinispan.filter

On Thu, Feb 26, 2015 at 3:57 AM, Galder Zamarreño <galder(a)redhat.com&gt; wrote: I agree they are very similar. Each one fulfills a different purpose. Originally only the 1 set of classes was used, but event filters evolved to have new requirements (oldValue, oldMetadata, retry, event type) that don't make sense for normal filtering. The regular KeyValueFilter, KeyFilter, Converter classes are still used when filtering existing entries (CacheLoader, EntryIterator). Also the simpler filter & converter will be able to be used as stepping stones for Streams when we move to Java 8 (although a tweak to the interface(s) will probably be required). The CacheEventFilter/CacheEventFilterConverter are only used when using events. The other simpler filters are used in all other cases.. The classes we talked about removing were the *Factory classes for the various filters. We can discuss converging the ones you mentioned here, but IMO the provided functionality has diverged quite a bit, which would make having a consistent API very ugly for one or both of the use cases. I would say from a remote event perspective you are correct. However once we add entry iteration for remote, we would want to use the more simplified interfaces.