W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1998

Re: cached resources

From: Paul Pazandak <pazandak@OBJS.com>
Date: Fri, 23 Jan 1998 10:58:00 -0600
Message-ID: <34C8CC17.B5F192B1@OBJS.com>
To: www-jigsaw@w3.org


Yves Lafon wrote:

> On Thu, 22 Jan 1998, Gil Hansen wrote:
>
> > How can one tell if a resource being downloaded is obtained from the cache
> > or from the remote host?
>
> If Jigsaw give the resource from the cache, the ingoingFilter of
> CacheFilter will return a Reply, you can use that.
> Another thing is to detect the Age: 0, but clearly, it is a hack :)
>

According to the docs ingoingFilter procesing should stop if a non-null Replyis
returned. Shouldn't this mean that no other ingoingFilters are called when the
CacheFilter returns a non-null Reply? In our test cases, the ingoingFilters are

still being called.  What is the purpose of calling the other ingoingFilters if
a
Reply was returned by the CacheFilter? Subsequent filters which attempt to
modify a request would be useless. However, filters that authorize access, for
example, would still be useful... but, it doesn't appear that Jigsaw can
support
both types. Unless, of course, one could place ingoingFilters BEFORE the
CacheFilter (e.g. custom authorization).

Further, ingoingfilters are only passed in requests, so other ingoingFilters
wouldn't know if a non-null Reply exists would it? But rather, it looks like
we'd have  to modify Jigsaw instead. Is this true?

Regards,

Paul.


> ...

>      /\          - Yves Lafon - World Wide Web Consortium -
>   /\ /  \                Architecture Domain - Jigsaw
>  /  \    \/\
> /    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org

   --

********************************************************************
Paul Pazandak                                      pazandak@objs.com
Object Services and Consulting, Inc.             http://www.objs.com
Minneapolis, Minnesota 55420-5409                       612-881-6498
********************************************************************
Received on Friday, 23 January 1998 11:55:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:27 GMT