Hi Marko, I've addressed some of your concerns by re-using a single thread pool for multiple schedule calls in the current master. The original use case was one set of scheduled tasks running for the lifetime of my application. If you can suggest improvements to cover other use cases with more stopping/starting scheduled tasks and automatically cleaning up the executor service if it's no longer needed that would be great.
Adam Clements On Fri, Jan 18, 2013 at 9:50 PM, Marko Topolnik <marko.topol...@gmail.com>wrote: > > This looks great. I was building a couple of applications that run >> periodic tasks/services on top of quartzite, but I'll definitely play with >> this. Much nicer scheduling syntax, and the lack of a single stateful >> scheduler feels much more Clojurian (and cleaner, too). >> > > Behind the apparent elegance is a design that could be wasteful with > system resources, starting another thread with each invocation of * > schedule* and leaving the executor service running after the future is > cancelled. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
