Re: LWP .01

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Roy Fielding: "New directory structure?"
• Previous message: Martijn Koster: "Re: LWP .01"
• Maybe in reply to: Joel Scotkin: "LWP .01"
• Next in thread: Joel Scotkin: "Re: LWP .01"

>The proxy code has moved from place to place during the development.  I think 
>the current location is reasonable.  Martijn might be able to elaborate on 
>this.
>
>Another matter is that the "get" script ought to have some way to set up 
>proxying.  Code donations are appreciated.

Hmmmm, that doesn't sound right.  Proxying is a library issue that
can be handled entirely by the library -- why make all clients do
the same work?

BTW, I just invented a new mechanism for URI resolution that may
replace the existing proxy_* environment variables.
I need to finish the specification, but it uses a client configuration
table (what I call a "URI Resolution Table").  See if you can guess
how it works just by looking at the format:

=================
www-uri-table/0.1
#
#PREFIX			HANDLER	  REPLACEMENT				AUTH
#
wais:			proxy	  http://wais.com/			Y
ietf:			replace	  file:/home/roy/ietf			N
ietf:/rfc		replace	  ftp://ftp.ics.uci.edu/pub/ietf	N
ietf:			replace	  http://ds.internic.net		N
http://info.cern.ch	replace	  http://www.w3.org			Y
http://hardcore.com	internal  block					Y
http:			internal  wwwhttp				Y
ftp:			internal  wwwftp				Y
news:			internal  wwwnews				Y
gopher:			internal  na					Y
telnet:			external  (xterm -c "telnet %HOST %PORT")	Y
=================

There is actually a lot more to it, including a standard for retrieving
initial resolution tables from a replicated central registry.

.....Roy   ;-)

• Next message: Roy Fielding: "New directory structure?"
• Previous message: Martijn Koster: "Re: LWP .01"
• Maybe in reply to: Joel Scotkin: "LWP .01"
• Next in thread: Joel Scotkin: "Re: LWP .01"