Closed jaredly closed 9 years ago
I don't want to sound like a pessimist, but this library is dying. We are just keeping it alive because of the lack of replacements (which I hope isn't too far away). Your time and effort would be better spent on one of the alternatives.
That being said, the best way to contribute with features is to simply fork rust-http, make a working implementation and send a pull request. It will most likely be accepted if it works.
Right. Just building something with iron, which uses rust http
On Thu, Nov 20, 2014, 12:26 PM Erik Hedvall notifications@github.com wrote:
I don't want to sound like a pessimist, but this library is dying. We are just keeping it alive because of the lack of replacements (which I hope isn't too far away). Your time and effort would be better spent on one of the alternatives.
That being said, the best way to contribute with features is to simply fork rust-http, make a working implementation and send a pull request. It will most likely be accepted if it works.
— Reply to this email directly or view it on GitHub https://github.com/chris-morgan/rust-http/issues/182#issuecomment-63864284 .
I see. Well, it seems like Iron may switch to hyper some day in the future. @reem can tell you more about that.
I can't give you any pointers to how you can implement those features, besides by following their standards, since my HTTP knowledge is quite limited. It's up to you how you want to proceed, but you are most welcome to contribute to rust-http if you feel like it. It's always appreciated. :)
I saw it says "we know this is missing"; how would I go about adding it?