Ok. What then I think a couple of commands on top of the sling service would do the trick. The extender part can be added on top of that too, but that's a different area imho.
On Mon, Jul 25, 2011 at 16:08, Ioannis Canellos <ioca...@gmail.com> wrote: >> >> I guess the part I'm still missing is the use cases for wrapping Timer >> or ScheduledExecutorService. ;-) > > > The way I see it it's not about wrapping, but its about managing. > > So some uses could be: > a) List the scheduled/recurring tasks. > b) Cancel a task. > c) reschedule a task. > d) pause/resume the execution of a task. > > On top of that, the fact that we can have a single shared thread pool that > is going to be used to execute those tasks has value on its own. > > -- > *Ioannis Canellos* > * > http://iocanel.blogspot.com > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > Apache ServiceMix <http://servicemix.apache.org/> Committer > Apache Gora <http://incubator.apache.org/gora/> Committer > * > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
