Jakob Buchgraber 220660e351 Deregistration of a Channel from an EventLoop ... Motivation: After a channel is created it's usually assigned to an EventLoop. During the lifetime of a Channel the EventLoop is then responsible for processing all I/O and compute tasks of the Channel. For various reasons (e.g. load balancing) a user might require the ability for a Channel to be assigned to another EventLoop during its lifetime. Modifications: Introduce under the hood changes that ensure that Netty's thread model is obeyed during and after the deregistration of a channel. Ensure that tasks (one time and periodic) are executed by the right EventLoop at all times. Result: A Channel can be deregistered from one and re-registered with another EventLoop.		2014-08-11 15:28:46 -07:00
..
src	Deregistration of a Channel from an EventLoop	2014-08-11 15:28:46 -07:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2013-12-22 22:06:15 +09:00