You lost me at actually ;) but if you have some code or even a gist showing how a user
would use and interact with these changes, I can give you some feedback on the use cases I
had in mind and if they fit.
On 25 sept. 2014, at 15:20, William Burns
<mudokonman(a)gmail.com> wrote:
Actually while working and thinking on this it seems it may be easiest
to exclude the usage of KeyValueFilter in the listener pieces
completely and instead leave the annotation as it is now. Instead the
provided CacheEventFilter would be wrapped by a KeyValueFilter
implement that just called the new method as if it was a create event
for each value while iterating on them. I am thinking this is the
cleanest. Do you guys have any opinions? It would also keep intact a
lot of existing code and APIs.