> For the single threaded point, I have added in to the documentation that
> tasks with a non-trivial running time should fire futures in order to avoid
> affecting subsequent scheduled tasks, which I think is a reasonable
> restriction to make given the resulting simplicity.
>
I agree, this i
Ah, thanks for the tip. I have now released 0.1.2 which is unchanged apart
from this fix (not leaking ExecutorServices) and improved documentation.
For the single threaded point, I have added in to the documentation that
tasks with a non-trivial running time should fire futures in order to avoid
a
There is no need to wrap the Executor Service in a* delay* because it
already implements lazy-start semantics. From the *ThreadPoolExecutor*
Javadoc:
On-demand constructionBy default, even core threads are initially created
and started only when new tasks arrive, but this can be overridden
dyna
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
sto
> 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 appa
Adam,
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).
Thanks!
Jason Lewis
E
Hello Adam,
I knew about https://github.com/overtone/at-at. Your lib is pretty straight
forward and promising.
Cheers
On 17 January 2013 16:05, Adam Clements wrote:
> A URL would probably help: https://github.com/AdamClements/schejulure
>
>
> On Thursday, January 17, 2013 5:56:40 PM UTC, Adam
A URL would probably help: https://github.com/AdamClements/schejulure
On Thursday, January 17, 2013 5:56:40 PM UTC, Adam Clements wrote:
>
> So there are a few scheduling libraries around, I wanted one for cron-like
> job scheduling and my options were quite limited, there are things like
> clj-
So there are a few scheduling libraries around, I wanted one for cron-like
job scheduling and my options were quite limited, there are things like
clj-cronlike and quartzite but I found the syntax quite clunky and didn't
like the central stateful scheduler idea. There are also things like at-at,
