On Sep 13, 2012, at 10:35 AM, Sergey Beryozkin wrote:
> On 13/09/12 14:53, Santiago Pericas-Geertsen wrote:
>>
>> On Sep 13, 2012, at 7:17 AM, Sergey Beryozkin wrote:
>>
>>> When selecting the filters to be run, before a given selected resource method is invoked, what priority should be given to global filters as opposed to name-bound ones ?
>>>
>>> I know BindingPriority is there, but should name-bound filters be run first, and global filters afterwards, no matter of what their individual priorities are ?
>>
>> No, they are part of the same "post-matching chain". Therefore, should be sorted by binding priority regardless of their kind.
>
> I still think it should be used at least as a secondary key, which will do well in cases where no BindingPriority is used on filters.
There's always a default binding priority. I think this adds an extra rule to describe without any benefits. Priorities are inherent to filters/interceptors not the way they are bound IMO.
-- Santiago