Netty

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Slip in DefaultOioSocketChannelConfig (setAllowHalfClosure used to ignore argument)

HttpRequestEncoder should append '/' to absolute path requests only when needed

HttpRequestEncoder should append '/' to absolute path requests only when needed

[#1853] Optimize gathering writes for CompositeByteBuf that are only backed by one ByteBuffer

[#1853] Optimize gathering writes for CompositeByteBuf that are only backed by one ByteBuffer

[#1852] Fix bug in UnpooledDirectByteBuf.nioBuffer(...) implementation

[#1852] Fix bug in UnpooledDirectByteBuf.nioBuffer(...) implementation

copy all sliced buffers, fixes #1848

copy all sliced buffers, fixes #1848

[#1836] Add comment to explain why read is triggered

[#1836] Add comment to explain why read is triggered

Fix nioBuffer implementation for CompositeByteBuf

Fix nioBuffer implementation for CompositeByteBuf

[#1833] Replace ; with & only in the QueryString and not the whole URI. Also add test-case

[#1833] Add testcase for fix

[#1833] Add testcase for fix

No need to use an unreleasable buffer - just wrap an array

No need to use an unreleasable buffer - just wrap an array

Fix build error

Add the hello world HTTP server example to compare the performance against Netty 4

More efficient handling of incomplete writes.

The problem with the old way was that we always set the OP_WRITE when the buffer could not be written

until the write-spin-count was reached. This means that in some cases the channel was still be writable

but we just was not able to write out the data quick enough. For this cases we should better break out the

write loop and schedule a write to be picked up later in the EventLoop, when other tasks was executed.

The OP_WRITE will only be set if a write actual returned 0 which means there is no more room for writing data

and this we need to wait for the os to notify us.

More efficient handling of incomplete writes.

The problem with the old way was that we always set the OP_WRITE when the buffer could not be written

until the write-spin-count was reached. This means that in some cases the channel was still be writable

but we just was not able to write out the data quick enough. For this cases we should better break out the

write loop and schedule a write to be picked up later in the EventLoop, when other tasks was executed.

The OP_WRITE will only be set if a write actual returned 0 which means there is no more room for writing data

and this we need to wait for the os to notify us.

[#1833] Replace ; with & only in the QueryString and not the whole URI

[#1833] Replace ; with & only in the QueryString and not the whole URI

[#1830] Add testcase for write to not bound DatagramChannel impls and revert change in OIO as it breaks things as the udnerlying socket lazy binds

[#1830] Add testcase for write to not bound DatagramChannel impls and revert change in OIO as it breaks things as the udnerlying socket lazy binds

Make DatagramChannel impls .isActive() return true when the underlying Channel is open. This also fixes [#1830]

Make DatagramChannel impls .isActive() return true when the underlying Channel is open. This also fixes [#1830]

Allow to only register a Channel via AbstractBootstrap and bind/connect it later. Related to [#1829]

Allow to only register a Channel via AbstractBootstrap and bind/connect it later. Related to [#1829]