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

Actually "unstable"? #35

Closed
andyfleming opened this issue Aug 13, 2015 · 8 comments
Closed

Actually "unstable"? #35

andyfleming opened this issue Aug 13, 2015 · 8 comments
Labels

Comments

@andyfleming
Copy link

I noticed the repo description says "unstable". I'm not very familiar with the project. Is that still accurate?

@voidcontext
Copy link

The better question is: is this project still alive?

@WyriHaximus
Copy link
Member

WyriHaximus commented Sep 19, 2015 via email

@ephrin
Copy link

ephrin commented Dec 17, 2015

@WyriHaximus bw, where I can find the latest version fork? Or some red tests to implement? Wanna help with.
Currently experimenting with threaded app. So need normal PHP http stream server ;)
Todos at react#3 are still actual ones? Gimme the bone!)

@WyriHaximus
Copy link
Member

@ephrin cool! Lets see what about gzip encoding, should be fairly easy to get started? (The equivalent PR on react/http-client: reactphp/http-client#50.) I'll create issues for them when I get home. And yes to answer your question the TODO on #3 is still relevant.

@ephrin
Copy link

ephrin commented Dec 18, 2015

@WyriHaximus I don't think gzip encoding is the necessary feature for a server. But can try if it's a good point to start 👌

@WyriHaximus
Copy link
Member

@ephrin fair point but gzip encoding to send a gzipped result back to the client could be interesting

@ephrin
Copy link

ephrin commented Dec 19, 2015

🏭

@clue
Copy link
Member

clue commented Feb 10, 2017

Thanks for filing this ticket, I can assure you we're working hard on this 👍 This repo is under active development and has received quite a few updates in the last weeks, so it's anything but dead :)

We've filed ticket for all known issues and missing features and filed new milestones for the upcoming releases to keep track of this. This means that we'll likely remove the "unstable" comment soon once the major blockers have been resolved here 👍

I believe this has been answered, so I'll close this for now. If this problem persists, please come back with more details and we can reopen this 👍

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

No branches or pull requests

5 participants