- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 27 May 2008 15:11:27 +0200
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "Maciej Stachowiak" <mjs@apple.com>, "Laurens Holst" <lholst@students.cs.uu.nl>, public-webapi@w3.org
On Mon, 26 May 2008 13:11:42 +0200, Julian Reschke <julian.reschke@gmx.de> wrote: > The problem that needs to be solved is that clients need a reliable way > to set a header. > > Issues with the current spec are: > > - implementations that preset headers on object creation This is solved. > - implementations *adding* values before the request is being made This is solved. > - library code that acts on an existing XHR instance but did not create > it, thus has no way what headers already have been set Can you point out which libraries have issues with this? It seems pretty weird that one library creates an object, invokes open() on it, and then lets another library set the request headers, and then let yet another set some more headers and invoke send(). > (the last one IMHO is the most important one, and the one that really > requires new functionality) I disagree. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Tuesday, 27 May 2008 13:11:40 UTC