[whatwg] HTML Cookie API
Darin Fisher
darin at chromium.org
Fri Feb 26 12:20:00 PST 2010
On Fri, Feb 26, 2010 at 12:04 PM, Diogo Resende <dresende at thinkdigital.pt>wrote:
>
>
> > No. pushCookies would be a way of pushing cookies to the
> > current js and
> > then you could call getCookie several times without defining a
> > callback.
> > It would be almost like:
> >
> > document.observe("cookieload", myAppLoad)
> >
> >
> > Right. My point was that you could implement pushCookies on top of
> > Adam's API.
> >
> >
> > -Darin
>
> Agree. Just like you could implement Adam's API on top of current
> browsers cookies spec :P
>
>
No, I don't think that is possible. Adam's spec reveals a lot of extra
information that "document.cookie" does not return. For example, it exposes
domain and expiry information.
But, I think your point was that it would be possible to simulate an
asynchronous API on top of a synchronous one. I agree that is possible, but
it would not perform very well.
Regards,
-Darin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100226/c46cd110/attachment-0001.htm>
More information about the whatwg
mailing list