Correct.
--
Sent from a mobile device.
Yes. Worker and WorkerPool have been replaced with EventLoop to simplify them significantly.
--
Sent from a mobile device.
Hi,
Without knowing the full internal details of Netty(hence my q could be stupid) let me ask the following q's
1) "A user can add and remove a channel from event loop whenever he/she wants" -> If we have multicore machines is there a strategy to create event loops themselves? Meaning on a 32 core machine would there be 32 event loops? If so, how do you assign new socket channels to event loops for e.g. round robin? Also are there options to set thread affinity etc.
2) Any plan to go down the disruptor way of IPC? They seem to have the fastest numbers published.
Regarding API, I have following suggestion. There should be a simple startServer(int port, ChannelInitializer factory) added.
It will be of no use to advanced users. However anybody beginning with Netty will be overwhelmed at the number of options(low level transport stuff like tcp no delay, backlog etc) needed to provide to just start a server.
Thanks,
Abraham Menacherry.
Try this:
--
Sent from a mobile device.