- From: Nico Williams <nico@cryptonector.com>
- Date: Mon, 11 Feb 2013 09:18:49 -0600
- To: Roberto Peon <grmocg@gmail.com>
- Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Zhong Yu <zhong.j.yu@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, Martin J. Dürst <duerst@it.aoyama.ac.jp>, James M Snell <jasnell@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Mon, Feb 11, 2013 at 1:38 AM, Roberto Peon <grmocg@gmail.com> wrote: > Also... nothing stops a site from implementing something like what Nico > described today with what already exists in HTTP, though the logic would be > encoded in the server business logic and page javascript instead of done > automatically by browser and server. I don't see how to do this without JS and without redirects. Also a standard way to do this seems much better than ad-hoc ways. Finally, this is clearly better than stateful compression as discussed in earlier threads -- at least for cookies. Nico --
Received on Monday, 11 February 2013 15:19:16 UTC