Jonathan S. Shapiro wrote:
>
> > I agree that the filter may not show the content to the user. But that
> > doesn't mean the filter should be permitted to change the "file".
>
> We are having a philosophical disagreement about the meaning of the
> word "change." My point, I think, is that the distinction between
> filtering and modification is smaller than it at first appears.
Hmmm. What I'm getting at is, I think, that there is a resource which the filter supposedly filters. OK, it may not actually filter it, it may substitute something different. So, when you view that resource through the filter, you are at the mercy of the filter. However, if I view the same resource by another route, I am only at the mercy of the filter if the filter has permission to modify the resource.
Is that clearer?
Cheers,
Ben.
-- Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org and Technical Director|Email: ben@algroup.co.uk | A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/ London, England. |"Apache: TDG" http://www.ora.com/catalog/apache