[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Simple] RE: Comments Event Filter Function -01
Comments inline Hisham
/gf
> Removing a filter is done in one way. Replacing a filter is
> done in another way. Two filters to the same user is an
> error. Having those 2 filters appear in the same request or
> in separate requests does not make a difference. We shouldn't
> overload the functionality. If something is clearly an error
> (trying to replace a filter in a different way than is
> specified), then the client must be told about it.
>
I dont get it.
To modify an existing filter for a resource. I have 2 possible alternatives here :
1) Use the same filterid with a new content.
2) Use a new filterid that implicitly removes the old filter for that user and replace it with the new filter. That respects the rule of having one filter per resource.
You seem to say that 2 is an error, and we should do that in 2 steps, first an explict remove, then add the new filter.
Can U elaborate on the rationale for that.
Does it causes confusion for other cases
> >
> > Next, in the third paragraph, you have the example on
> > myboddies at mydomain.com & bob at mydomain.com, it seems to me
> > that the domain must be different for the RLS to extract the
> > filter and propagate it, so Bob should have a different
> > domain for the statement to apply.
>
> The example is correct. A filter is not propagated if Bob was
> not part of the list, but is part of domain.com.
Your statement is true but thats not what the text in the draft is saying.
If Bob was on the list and part of the domain, I dont see where to would you propagate the filter.
I had one comment I forgot to mention.
In section 5.2.1 you talk about mismatch between the R-RI in SUBSCRIBE and URI in the filter.
It would help to expand what mismatch means.
I know you cover it in several places in the document.
Optionally refer to the section where one can find the pertinent text.
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple