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

Support for Netty 4.0.30-Final #22

Closed
afkham opened this issue Aug 14, 2015 · 6 comments
Closed

Support for Netty 4.0.30-Final #22

afkham opened this issue Aug 14, 2015 · 6 comments

Comments

@afkham
Copy link
Contributor

afkham commented Aug 14, 2015

I have started working on migrating this code to Netty 4. You can find the work in progress code at https://github.com/afkham-azeez/netty-http. Do you have plans to move to Netty 4 in the near future? If so, I will be happy to provide a GitHub PR.

@nitinmotgi
Copy link
Contributor

We would love to have this patch. Send in the PR when ready. Thanks for your contribution.

@cdancy
Copy link

cdancy commented Oct 6, 2016

@afkham @nitinmotgi @chtyim any updates here? Even if not implemented by this developer any plans within cask to bump to a newer version of netty?

@pims
Copy link

pims commented Jan 20, 2017

I just stumbled on netty-http and it seems to be a good foundation for what we’re trying to build.
My knowledge of Netty is very limited, but if there is an common effort to port to Netty 4, I’d like to contribute in any way I can.

@afkham what’s the status of your fork? Need help finishing it?

@blling
Copy link

blling commented Mar 28, 2017

nothing happend?

@chtyim
Copy link
Contributor

chtyim commented Oct 6, 2017

PR opened to upgrade to netty-4.1 https://github.com/caskdata/netty-http/pull/46

@chtyim
Copy link
Contributor

chtyim commented Oct 10, 2017

Issue resolved with the upgrade to netty 4.1

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

No branches or pull requests

6 participants