Re-using same XHR object for multiple requests doesn't work #120
Labels
Comments
|
I thought I replied to this one... Interesting, didn't even know that was a thing. What's the benefit of using the same xhr object more than once? I've marked this as a bug as it should be supported by XHook. |
|
Sorry, I created an issue for both xdomain and xhook. I'm not quite sure what the benefit is, I assume to minimise memory consumption when making a lot of synchronous requests. Regardless, some libraries use xhr objects this way such as https://github.com/scottjehl/Respond |
enure
added a commit
to enure/Respond
that referenced
this issue
Dec 10, 2014
jpillora
added a commit
that referenced
this issue
Dec 13, 2014
…) - global find/replace all affected links, updated docs, fixed deprecation warning, bumped xhook (closes #120), user controlled xhook.addWithCredentials (closes #125 @DveMac), fixed timeout checks (closes #118 @rcambrj), added log,warn,timeout hooks (closes #104), added xhr abort on (iframe) timeout (fixes #102)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vanilla xhr allows you to reuse the same xhr object for multiple requests, xdomain breaks this piece of functionality.
The text was updated successfully, but these errors were encountered: