W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1996

Desired feature - API to proxy-cache database

From: Anselm Baird-Smith <abaird@w3.org>
Date: Mon, 26 Aug 1996 21:14:19 +0500
Message-Id: <9608270114.AA11986@www18.w3.org>
To: mark@intraspect.com
Cc: www-jigsaw@w3.org
Mark Friedman writes:
 > It would be nice if the upcoming proxy cache was architected so that you
 > could easily plug in your own storage mechanism (e.g. an OODB). Related
 > to that, it would be convenient to be able to access the cache from the
 > non-proxy parts of Jigsaw. And last but not least, it would be nice to
 > have the a filtering and resource mechanism for proxyied resources
 > similar to the standard mechanisms for the regular server.

Jigsaw uses a jdbmResourceStore (or more fundamentaly a ResourceStore)
to store cache resources infos (with link to a file for the content of
the resource). If you write a resource stoire that uses a OODB, then
you would probably  be able to use it instead of the jdbmResourceStore
that the proxy current uses (BTW the jdbmResourceStore is built on top
of w3c.tools.dbm).

Filtering is more tricky. You can apply filters to the ProxyDirectory
itself, but they will then apply to all the cached resources (although
you may write a fancy filter that will filter the resource on which to
act...). For example proxy authentication uses the same
w3c.jigsaw.auth.GenericAuthFilter applied to the ProxyDirectory.

The cache is accessible through Jigsaw HTTP client API. (which can be
accessed through the std java HTTP API, if you will). But it is
defintely hidden below this. The Jigsaw HTTP client API has an
equivalent filtering mechanism, and the cache is architectured as a
(client-side) filter.

Received on Monday, 26 August 1996 21:14:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:29 UTC