I'm building a reporting backend where users can schedule a report to be run weeks / months in advanced. I've used Quartz in the past for this kind of things but my use case isn't that complex and I think I can get away with just using the akka scheduler (plus I just don't like Quartz and would like to avoid the dependency if I can). My only requirement is that the user gives me a date time instant that they want the report to run, so I can easily figure out the delay to give the akka scheduler in seconds. Also I don't need need any guarantees about the report running at exactly the correct instant, it could be off by even an hour and I would be fine. My concerns are if the akka scheduler can even handle scheduling something this far in advanced, I imagine that it has a hard limit on whatever the max integer is. Also, I'm not sure what the best approach would be to handle jvm restarts or crashes. In this case I would need to have some sort of persistence so that the scheduler could be restarted. Is this something that akka persistence could help me with or have to roll something myself?
Cheers, Greg -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
