Skip to content
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

Implement chunked transfer encoding #38

Closed
clue opened this issue Sep 3, 2015 · 5 comments
Closed

Implement chunked transfer encoding #38

clue opened this issue Sep 3, 2015 · 5 comments

Comments

@clue
Copy link
Member

clue commented Sep 3, 2015

Refs #5

@clue
Copy link
Member Author

clue commented Mar 10, 2017

Receiving incoming responses with chunked transfer encoding has been resolved via #58.

We may still want to implement sending requests with chunked transfer encoding.

@ghost
Copy link

ghost commented Jul 11, 2019

@clue Since this package links now to the higher level implementation buzz, do we still want to implement sending chunked transfer encoding in this component? This would mean moving the logic from buzz to this component (which should probably be fairly straight forward).

@WyriHaximus
Copy link
Member

@CharlotteDunois yes that's the goal

@clue
Copy link
Member Author

clue commented Jul 12, 2019

What @WyriHaximus said :-)

The (longer-term) goal is to make https://github.com/clue/reactphp-buzz redundant in the future so that we can deprecate it and only rely on @reactphp's HTTP component 💪

@clue
Copy link
Member Author

clue commented Jul 13, 2020

I'm closing this as it is already supported by the new HTTP client that has been merged into react/http via reactphp/http#368 :shipit: You should upgrade as per #152 👍

@clue clue closed this as completed Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants