andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,130 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
2ded0dd6fe
Go to file
Trustin Lee 2ded0dd6fe Fix data corruption in FileRegion transfer with epoll transport 
Related issue: #2764

Motivation:

EpollSocketChannel.writeFileRegion() does not handle the case where the
position of a FileRegion is non-zero properly.

Modifications:

- Improve SocketFileRegionTest so that it tests the cases where the file
  transfer begins from the middle of the file
- Add another jlong parameter named 'base_off' so that we can take the
  position of a FileRegion into account

Result:

Improved test passes. Corruption is gone.
2014-08-13 16:58:35 -07:00
all Add MQTT protocol codec 2014-06-21 16:51:37 +09:00
buffer Use heap buffers for Unpooled.copiedBuffer() 2014-08-13 15:09:41 -07:00
codec Implemented FastLZ compression codec 2014-08-12 15:15:54 -07:00
codec-dns Fix buffer leaks in DnsResponseDecoder and DnsResponseDecoderTest 2014-08-04 14:05:02 +02:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Introduced HTTP/2 frame to HTTP/1.x translation layer. 2014-08-12 12:31:26 -07:00
codec-http2 Introduced HTTP/2 frame to HTTP/1.x translation layer. 2014-08-12 12:31:26 -07:00
codec-memcache Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-mqtt Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-socks Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-stomp Fix a resource leak in StompSubframeAggregatorTest 2014-08-11 10:46:17 -07:00
common Deregistration of a Channel from an EventLoop 2014-08-11 15:28:46 -07:00
example Introduced HTTP/2 frame to HTTP/1.x translation layer. 2014-08-12 12:31:26 -07:00
handler [#2721] Improve Traffic Shaping handler 2014-08-13 02:21:07 +02:00
license Implemented FastLZ compression codec 2014-08-12 15:15:54 -07:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:27:28 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Fix data corruption in FileRegion transfer with epoll transport 2014-08-13 16:58:35 -07:00
transport Revert "[#2761] ChannelOutboundBuffer can cause data-corruption because of caching ByteBuffers" 2014-08-13 21:46:36 +02:00
transport-native-epoll Fix data corruption in FileRegion transfer with epoll transport 2014-08-13 16:58:35 -07:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Make Nio/EpollEventLoop run on a ForkJoinPool 2014-08-11 15:28:46 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:34:51 +09: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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented FastLZ compression codec 2014-08-12 15:15:54 -07:00
pom.xml Reduce the execution time of maven-antrun-plugin 2014-08-13 15:45:00 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:11 +09: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

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.