Repository navigation
Merge into Http component and deprecate HttpClient component #78
Description
Opening this for the reference and to raise awareness. Note that there's an ongoing discussion as to whether this component should be merged into the Http component.
See reactphp/http#148 for details.
Activity
andig commentedon May 5, 2017
I'm currently looking into this and am a bit stumped on how to convert a Psr
StreamInterfaceinto a reactReadableStream.To be more precise I'm trying to use ringcentral
StreamWrapper::getResource()to convert fromStreamInterfaceintoReadableStreamwhich fails:Any ideas? Either this is not an "easy pick" or just beyond my skills :/
clue commentedon May 5, 2017
@andig It sounds like this might be related to #41 instead of this ticket? It's my understanding that #41 has priority first and once that's addressed, merging the two components should be an easy pick
andig commentedon May 5, 2017
@clue thank you. I didn't realize there was already work going on. Better letting you guys do your magic :)
mdrost commentedon Jun 17, 2017
Is it possible that when this components will be merged into react/http then this repository could become something like react version of GuzzleHttp with all Psr7 goodies (better version of clue/php-react-buzz)?
WyriHaximus commentedon Jun 17, 2017
Define
and
cause not sure what exactly you're looking for 😉
clue commentedon Jul 12, 2020
Superseded and closed via reactphp/http#368 / #152