W3C home > Mailing lists > Public > public-bpwg@w3.org > September 2009

CT - interacting with the user

From: Jo Rabin <jrabin@mtld.mobi>
Date: Mon, 28 Sep 2009 11:37:54 +0100
Message-ID: <4AC09202.1050100@mtld.mobi>
To: Public BPWG <public-bpwg@w3.org>

The requirement on the proxy only kicks in when they are doing things 
that mean they are stepping out from behind the transparency you discuss.

So I'd prefer to remain silent on this. Many of the proxies we are 
talking about in this case, do in fact communicate directly with the 
user. I don't think we should mandate the nature of the communication.


 From Chaals:

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



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 Monday, 28 September 2009 10:38:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:54 UTC