The current vision is that filters will be implemented agnostic to the overall processing architecture - there may be subscribers using lucene dsl as part of the initial streams implemetation- but the interface won't dictate how a subscriber filters it's activities - I don't know that we've figured out whether the subscriber delegate tells the aggregate its filter via an interface or whether aggregator tells each subscriber about every activity and the subscriber filters - either way - you can implement filters however you want - provides they adhere to the common filter interface (which to my recollection is very simplistic)
On Monday, June 3, 2013, Lavender, Beth A wrote: > Many of our current systems that will feed the integrated activity stream > are noisy. For example, if I update a page 4 times in 5 minutes it > generates an activity for each one. I want to be able to set rule for > discard the last n activities if they have the same actor, verb, and object > in x time frame. > > This assumes a sub processor that detects the pattern and takes an action > described in a rule. Where do rules and sub processors fit in this > architecture? Is anyone doing this in their existing systems? > >
