I think a more robust design would be to make a system that works without Netty and then use Netty's connection handler to go between the two. This way, if you decide to move away from Netty in the future, you can do so with minimal rewiring.
1 - Great minds, thinking alike. – duffymo Sep 30 at 18:29 To be fair, we had different reasons. :) Yours was for easier testing.
Mine was for easier migration. Both are something you need to keep in mind when designing software. – glowcoder Sep 30 at 18:34 Agreed.
Nice answer. Thanks for the clarification. – duffymo Oct 1 at 2:18.
If you put all that functionality into interface-based POJOs, rather than a Netty connection handler, you'll find it easier to test it without having to fire up Netty. Once you have all those objects working and tested, then give them to a connection handler and let them do the work. The connection handler just orchestrates your POJOs to fulfill its requests.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.