W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > June 1999

Re: An Open And Extensible Personalised Proxy Framework

From: Daniel Dardailler <danield@w3.org>
Date: Fri, 04 Jun 1999 09:32:53 +0200
Message-Id: <199906040732.JAA14303@www4.inria.fr>
To: Wayne Myers-Education <wayne.myers@bbc.co.uk>
cc: WAI ER IG List <w3c-wai-er-ig@w3.org>

> In terms of client-side proxy filtering, I've been looking at the following
> five-piece plan:

My experience (working with other W3C groups, like Ecommerce) is that
there isn't a portable solution for client-side proxy, and you have to
adapt your setting and filter to IE, to Netscape, to Lynx, etc.

For Lynx, for instance, there's a way to compile it (so not supported
in every binaries) so that it recognizes some URI schema (say
xhttp://) as special and runs a filter thru them. See lynx documentation.

For Emacs/W3, you need to write you own piece of elisp.

For Netscape, there's a panel (Automatic Proxy Configuration) that
let's you play with client side script. (see
http://www14.netscape.com/navigator/admin/v3.0/proxy.html)

etc.

It's too bad that there isn't a simple client side CGI interface,
fired thru some .mailcap file, like for helpers, that would let anyone 
install a filter on the client side.
Received on Friday, 4 June 1999 03:32:58 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:33 GMT