W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: multiplexing -- don't do it

From: Roberto Peon <grmocg@gmail.com>
Date: Mon, 2 Apr 2012 15:21:00 -0700
Message-ID: <CAP+FsNeW1UFrwK6c-N7M8t=i3h67PuZkHzQgq9Xho7twPxOhiw@mail.gmail.com>
To: J Ross Nicoll <jrn@jrn.me.uk>
Cc: "Adrien W. de Croy" <adrien@qbik.com>, Mike Belshe <mike@belshe.com>, Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
And the server/content provider folk as well-- both client and site
participate in policy setting (and for good reasons on both sides).
-=R


On Mon, Apr 2, 2012 at 3:10 PM, J Ross Nicoll <jrn@jrn.me.uk> wrote:

>  On 02/04/2012 22:59, Roberto Peon wrote:
>
>
>
>>
>> These are people who can hardly use a mouse you're trying to get them to
>> set up proxy config in their browser?
>>
>>
>
>  I'm familiar with these kinds of people and working with them. I'd
> imagine that the ISP would give them an installer which would find and set
> config for these programs without the user having to do it themselves or
> something similarly easy.
>
>
> Probably, but if proxy information could be added into DHCP, DNS or
> similar, isn't that going to be a lot more straight-forward than everyone
> having to provide their own installers through a separate distribution
> channel?
>
> If a proxy can intercept secure traffic, that needs to be made really
> clear to the user (especially in cases such as those "FREE INTERNET!!!"
> ad-hoc networks that turn up in airports and similar), but that's
> presumably something for the browser peeps to figure out.
>
>
Received on Monday, 2 April 2012 22:21:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:59 GMT