W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1996

PUTs and Proxies

From: Anselm Baird_Smith <abaird@www43.inria.fr>
Date: Wed, 13 Nov 1996 10:15:35 +0100 (MET)
Message-Id: <199611130915.KAA29174@www43.inria.fr>
To: Gordon Dakin <gad@hunchuen.crystaliz.com>
Cc: www-jigsaw@w3.org
Gordon Dakin writes:
 > 
 > 
 > 
 > I am attempting to combine proxying with GETs & PUTs, but I am a novice
 > at proxying, so I would appreciate any help you can offer.  The scenario is:
 > 
 > Client requests are handled by my own resource class, which is (in theory)
 > installed as the root resource (an extension of HTTPResource or FileResource).
 > To process a request, the resource decides whether to GET or PUT the file,
 > or to perform some other action, based on external criteria.  If the URL
 > points to a foreign server, the GET/PUT is referred there, where a "pure"
 > Jigsaw (without my extensions) will hopefully handle the request, using
 > FileResource's GET or PUT method.
 > 
 > As a novice to proxying in Jigsaw, my questions are: can my new resource
 > invoke jigsaw's proxying capabilities in the middle of an ongoing request
 > (when a foreign server is indicated), and if so, what actions are required? 
 > And would the original request create a new GET/PUT request on-the-fly for
 > the foreign Jigsaw, or can it just redirect itself to the foreign Jigsaw?   

- Yes you can invoke proxying in the middle of a request.
- Check w3c.jigsaw.proxy.ForwardDirectory to see how it works.

BTW: It's not a good idea to subclass FileResource to create a root
resource, since FileResource lookup capabilities are very reduced.

Anselm.
Received on Wednesday, 13 November 1996 04:15:57 GMT

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