-
Notifications
You must be signed in to change notification settings - Fork 713
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
Expose response reader without reading response #87
Comments
@perdasilva Thanks for creating an issue, once done I will ping you. |
@perdasilva I would like to know how soon you need this feature. Based on that I will plan it. Please let me know. |
@jeevatkm - I am also interested in this feature and need it to continue with a project I'm working on. |
@adeanzan Thank you |
ASAP would be great. As it is now, we are mixing b/w resty and net/http. Would be nice to just rely on resty ^^ |
Thx for picking this feature up ^^ |
@perdasilva @adeanzan Thanks, understood. Once branch is ready I will ping you. So that you can try before merging into master. |
@perdasilva @adeanzan I have added this feature on branch expose-response-body of commit 6a77f10
To get the body Please refer to methods godoc. I look forward to feedback and improvements. |
@perdasilva @adeanzan Did you get a chance to try it out? Awaiting your feedback then I will merge it master. |
@jeevatkm Just gave it a try and it worked great! I appreciate the quick implementation. |
@adeanzan Thanks for the feedback. |
Shit dude, I'm so sorry - I totally missed your tag on the previous message. Thank you for implementing the change!!! |
That's okay @perdasilva. Give it try and let me know, its currently on master; not yet released. |
I would like to get access to the response reader without the response first being read by resty. This would allow me to stream (e.g. to stdout) the response as it comes, rather than resty buffering it until it finishes.
The text was updated successfully, but these errors were encountered: