- From: Charles McCathieNevile <chaals@opera.com>
- Date: Sun, 27 Sep 2009 21:44:39 +0200
- To: "Mobile Web Best Practices Working Group WG" <public-bpwg@w3.org>
Proxies by their nature don't generally interact directly with the user. I
think it is worth explaining what we mean by "inform the user", "advise
the user", "allow the user to..." etc.
One approach is for the proxy to ship content explicitly to the user
(instead, presumably, of what the user actually asked for). Another is to
make flags available to the user agent which is accessing the proxy (e.g.
generating 300 responses, vary headers, or the like) which would allow the
UA to do whatever it normally does that allows the user to make choices.
This question is important because at the moment we seem to be implying
requirements on the proxy which either make assumptions about the UA, or
contradict the goal of letting the user simply go to the content they
asked for (which is the service proxies generally provide, trying to be if
not transparent in teh terms of the document then at least as invisible as
possible).
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Sunday, 27 September 2009 19:45:20 UTC