- From: Kris Zyp <kris@sitepen.com>
- Date: Mon, 14 Apr 2008 11:25:20 -0600
- To: "Thomas Roessler" <tlr@w3.org>
- Cc: <public-appformats@w3.org>, "Web API WG \(public\)" <public-webapi@w3.org>, "Jon Ferraiolo" <jferrai@us.ibm.com>, "Close, Tyler J." <tyler.close@hp.com>, "Chris Wilson" <Chris.Wilson@microsoft.com>, "David Ross" <dross@windows.microsoft.com>, "Doug Stamper" <dstamper@exchange.microsoft.com>, "Eric Lawrence" <ericlaw@exchange.microsoft.com>, "Gideon Cohn" <gidco@windows.microsoft.com>, "Ian Hickson" <ian@hixie.ch>, "Jonas Sicking" <jonas@sicking.cc>, "Laurens Holst" <lholst@students.cs.uu.nl>, "Marc Silbey" <marcsil@windows.microsoft.com>, "Maciej Stachowiak" <mjs@apple.com>, "Nikhil Kothari" <nikhilko@microsoft.com>, "Sharath Udupa" <Sharath.Udupa@microsoft.com>, "Sunava Dutta" <sunavad@windows.microsoft.com>, "Zhenbin Xu" <zhenbinx@windows.microsoft.com>
> I don't know whether "most modern devs are using JSON", Yeah, I really don't have any data to back that up, I shouldn't make such claims :). But I think it is safe to say that many devs use it. > More generically, I don't think that new cross-origin APIs that > "just return a string" (but are clearly intended for structured > data) should be standardized (or shipped) given the experience > that's available. So you would be in favor of a responseJSON property? Kris
Received on Monday, 14 April 2008 17:33:57 UTC