andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
8,514 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
48b4502d1d
Go to file
Dan McNulty 48b4502d1d Move EmptyHttpHeaders.INSTANCE initialization to inner class. 
Motivation:

If the HttpUtil class is initialized before HttpHeaders or
EmptyHttpHeaders, EmptyHttpHeaders.INSTANCE will be null. This
can lead to NPEs in code that relies on this field being
non-null. One example is the
LastHttpContent.EMPTY_LAST_CONTENT.trailingHeaders method.

Modifications:

- Move HttpUtil.EMPTY_HEADERS to a private static final inner class
  of EmptyHttpHeaders called InstanceInitializer.
- Add tests, that when run in isolation, validate the fix for the issue.

Result:

Any initialization order of HttpUtil, EmptyHttpHeaders or
HttpHeaders will result in EmptyHttpHeaders.INSTANCE being initialized
correctly.
2017-11-17 16:31:09 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
buffer CompositeBytebuf.copy() and copy(...) should respect the allocator 2017-11-10 07:17:16 -08:00
codec [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-http Move EmptyHttpHeaders.INSTANCE initialization to inner class. 2017-11-17 16:31:09 +01:00
codec-http2 codec-http2: Improve h1 to h2 header conversion 2017-11-17 09:09:52 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
common codec-http2: Improve h1 to h2 header conversion 2017-11-17 09:09:52 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
handler Dont fire an SslHandshakeEvent if the handshake was not started at all. 2017-11-16 19:57:04 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Use Netty's DefaultPriorityQueue instead of JDK's PriorityQueue for scheduled tasks 2017-11-10 23:09:32 -08:00
resolver [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
resolver-dns Don't try to use UnixResolverDnsServerAddressStreamProvider when on Windows. 2017-11-13 20:26:38 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport Improved error message in FixedChannelPool 2017-11-13 20:29:07 +01:00
transport-native-epoll EpollSocketChannelConfig.getOptions() must not throw if TCP_FASTOPEN_CONNECT is not supported 2017-11-16 14:07:54 +01:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-native-unix-common EpollSocketChannelConfig.getOptions() must not throw if TCP_FASTOPEN_CONNECT is not supported 2017-11-16 14:07:54 +01:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02:00

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.