Re: [Simple] problem with filters and resource lists

[Hisham Khartabil <hisham.khartabil at telio.no>]

On Feb 15, 2006, at 2:26 PM, <Silvestr.Peknik at tietoenator.com> wrote:

> As I understand it now the order of the filters will be different for
> following situations:
>
> - List1 at RLS1, List2 at RLS2
> - F1 targeted to bob at 1.com / bob at 2.com respectively
> - F2 targeted to list2 at 2.com
>
> Situation 1:
> List1 at 1.com
> 	- list2 at 2.com
>
> List2 at 2.com
> 	- bob at 1.com
>
> Order of filters applied to bob: F2 (propagated to RLS2), F1 (kept by
> RLS1)


As I said, this part is implementation dependent. I would implement it 
in a way that RLS1 remembers that there will be subscription coming for 
bob at 1.com from a subscription it forwarded to RLS2. It will then apply 
F1 to the NOTIFY it sends to RLS2.

In any case, the subscriber needs to create the filters in a smart way 
that they don't conflict (like in the example you give below about 
<status>).

> Situation 2:
> List1 at 1.com
> 	- list2 at 2.com
>
> List2 at 2.com
> 	- bob at 2.com
>
> Order of filters applied to bob: F1, F2

This is correct.

Hisham

> The order is important because it can change the resulting 
> notification,
> e.g. if F1 excludes all <status> elements and F2 is triggered by change
> in <status> element. So we would have different results for the same
> filters based on the distribution of the resources.
>
> Is this behavior intended (if the scenarios are correct)?
>
> Silvestr Peknik
> TietoEnator


_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple