-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
Comments
The better question is: is this project still alive? |
The project is still active and worked on. One of the reasons it is still
unstable is because it's lacking full HTTP 1.1 support, we're working on
that. As far as stability goes for the HTTP parts we've implemented, they
are stable.
|
@WyriHaximus bw, where I can find the latest version fork? Or some red tests to implement? Wanna help with. |
@ephrin cool! Lets see what about gzip encoding, should be fairly easy to get started? (The equivalent PR on |
@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 👌 |
@ephrin fair point but gzip encoding to send a gzipped result back to the client could be interesting |
🏭 |
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 👍 |
I noticed the repo description says "unstable". I'm not very familiar with the project. Is that still accurate?
The text was updated successfully, but these errors were encountered: