-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Response streaming? #225
Comments
You mean like this?
I wouldn't use this library anymore. It's slow and more trouble than it's worth. Granted the built-in url library is written in precisely the wrong way, but I still prefer it to clumsily spawning a curl subprocess. |
Yes, that's what I'm doing. Aside from the problem of how to disconnect, the above code is not quite correct when something like "Content-Encoding: chunked" is used. But if you stick the hook in a 0-second timer so that it runs after
Sorry, do you mean Either way, what would you recommend? |
I wouldn't use |
Err, thanks, writing code is not the problem. It's all going up on GitHub in the end anyway. Was just wondering if there's a more established library I should be using instead. Cheers. |
I believe some nimrod is floating his own http library as an alternative to this one which he denigrates every chance he gets. Google around. |
Hi,
Is it possible to receive response data incrementally? E.g. for
Content-Type: text/event-stream
responses?I kinda managed to get it to work with
url
with anafter-change-functions
hook, but that seems hacky and there doesn't seem to be a clean way to interrupt an in-progress request.Thanks!
The text was updated successfully, but these errors were encountered: