Well a timer service is a different type of service. Not sure I can find you a good reference, but read for example the beginning of this article: https://lwn.net/Articles/735887/
"The other subsystem is just called "kernel timers"; it offers less precision but is more efficient in situations where the timer will probably be canceled before it fires." Something like a Timer#reset() method, which resets the countdown to the event, is not natural with a task scheduler, although you can surely emulate it sort of. They are related, but different. You can read about Linux timerfd_settimer or POSIX setitimer to get a better feeling for what a timer service might offer. On Wednesday, May 16, 2018 at 8:23:37 PM UTC+2, Norman Maurer wrote: > > I am not sure what exactly you are looking for but we have > HashedWheelTimer or EventLoop for this. > > What is missing here ? > > Bye > Norman > > > Am Mittwoch, 16. Mai 2018 20:19:19 UTC+2 schrieb Martin Furmanski: >> >> Hello! >> >> Did you ever consider exposing a pure timer service? I think a timer >> service would fit neatly in the framework as a general capability. You also >> already have the basic infrastructure of making it efficient, e.g. native >> timerfd-support on Linux. >> >> Best Regards, >> Martin Furmanski >> > -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/f60308fb-d1ea-464c-978b-35d13105c8be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
