> Anyhow, I'm not averse to having an asynchronous API, but I'd still like to
> enable workers to do this:
> setCookie("cookiestring")
> xhr.send();
>
> Forcing workers to do all of their cookie-laden network requests via a
> double-callback (set cookie, wait for callback, invoke xhr, wait for
> response) seems too cumbersome.Good point, I don't think there's a conflict between saying "its async" and "its gauranteed to be set for xhr's sent after having called setCookie (but prior to having received an async completion callback)"
