b58036aeea
Motivation: EmbeddedChannelId#hashCode() and equals() do not behave correctly if an instance is serialized and then deserialized. Additionally, EmbeddedChannel does not allow use of any other type of ChannelId, and EmbeddedChannelId is (mostly) a singleton instance. This creates a problem for unit tests that construct multiple EmbeddedChannels and expect each channel to have a unique ID. Modifications: EmbeddedChannelId is modified so equals() will return true and hashCode() will return the same value for any instance of the class. EmbeddedChannel is modified to allow a ChannelId to be specified when the channel is constructed. Tests added for both changes. Result: EmbeddedChannelId now behaves correctly when deserialized, and EmbeddedChannels can now have unique IDs.
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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
The 'master' branch is where the development of the latest major version lives on. The development of all other 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.