Hi! (Long time, no see... I have been very busy in the past two months... As a result, I haven't had any time to follow the discussions on the list... And the i18n stuff has been in a flux as well... But, after another couple of weeks things should get easier again and I'll have some time to contribute... ;-)) (Just wanted to give a short explanation for quite a long period of inactivity...)
Anyway, getting to the point: I need to write an application that would run regularly in the end of every working day. Seems like a natural task for a scheduler and that reminded me that Avalon used to have a scheduler implementation. I found the implementation from cornerstone but I cannot really figure out how exactly should I use it? My understanding the the following: I will deploy this scheduler service into Phoenix. Then I have the block available for use by other blocks. I will write a custom block that will look up the scheduler and will submit task(s) to it. Correct? Ok, now here are a couple of questions: * are there any examples/samples of code that would demonstrate the usage of the scheduling service? * or maybe even some documentation? (I couldn't find anything from CVS) * if I need to have a task to be run only on working days, how could I solve that? Should I schedule the task separately five times, each with one week delay? Or is there some automagical feature that would solve this issue for me? And BTW, what is the status of the database connection pooling code? Last time I remember, it was not very usable, any progress on this? Rgds, Neeme -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
