i agree this would be awesome. at the unhosted project we promote
"instant data liberation" to make APIs more accessible on the open
web, and this is exactly the sort of thing we need!
as soon as the user-agent has the access token, there is no reason to
deny html5 apps access to the resources, and most browsers now support
CORS headers, so if you're not adding them where appropriate, you're
basically lagging behind in compliance with open web standards. sadly,
lots of people still are, so i'm very happy to see that google is
taking the lead once more in open web tech awesomeness, and you are
picking this up in your API interfaces!
On Oct 5, 1:44 am, Vic Fryzel <
vicfry...@google.com> wrote:
> I don't think we send back the required header. We'll see about adding this
> for you.
>
> -Vic
>
> On Tue, Oct 4, 2011 at 3:56 PM, Constantine Vasil <
thst...@gmail.com> wrote:
> > as documented here:
> >
http://code.google.com/intl/fr/apis/documents/docs/3.0/developers_gui...
> > HTML5 supports CORS, the question is if Google Docs supports CORS too?
> > e.g. does it return the CORS enabled header:
> > Access-Control-Allow-Origin: *
any news on this since that conversation? is there a ticket we can
track?
thanks so much for making your API more open and more "webby" in this
way!
Cheers,
Michiel de Jong
Unhosted.org