- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sun, 08 Apr 2012 20:35:10 +0000
- To: "Nicolas Mailhot" <nicolas.mailhot@laposte.net>
- cc: "Adrien W. de Croy" <adrien@qbik.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
In message <6d282afce1d51732a6d9cdcfdcac0a8a.squirrel@arekh.dyndns.org>, "Nicol as Mailhot" writes: >Then if the protocol does not permit signaling progress, what the solution >would be? (educating users does not work, they've been brainwashed to refresh >at the slightest pause) I think it is a design-mistake for the proxy to react to the forced reload of a huge object, when is already busy processing that object and have not delivered it to any clients yet. Given that the client has not seen the object yet, the client has no basis for conclusing it is out of date, so the reloads should be ignored, the requests queued and once the object is processed, you can deliver it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Sunday, 8 April 2012 20:35:35 UTC