Periodic TimerTask in netty

[Lev Shock]

I still don't understand your point.
The "advantage of ExecutionHandler" has no relation to timers or triggers of
any kind. I am using ExecutionHandlers in my projects and enjoying all of
its advantages, so they are not "gone", I can assure you. And yes, I have
some periodic tasks which send data over network. They are managed by
ScheduledThreadPool, and  I don't find it "boring" in any way.
Netty is the framework which handles NETWORK events, not business logic
"events" of any kind. Your application may wish to send something to a
client for million reasons: when some timer expires, when user clicks some
button in GUI, when you receive signal from some hardware device, etc. Netty
just can not and should not know about all these reasons. If you need to
write something using Netty, you just call channel.write(..). That's it. I
cannot imagine any simpler way to do this.
And yes, "business object needs to be designed carefully" - this is always
true, and no framework will design your business logic for you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20110905/b8a8d93f/attachment-0001.html