Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Recurring Task Features #1

Open
bruce-w opened this issue Sep 16, 2014 · 1 comment
Open

New Recurring Task Features #1

bruce-w opened this issue Sep 16, 2014 · 1 comment

Comments

@bruce-w
Copy link

bruce-w commented Sep 16, 2014

Hi,
Currently Revalee supporting only daily and hourly recurring periodic type.
it would be better if it support the Start Date and End Date for the job.
Also need to support new periodic types like Weekly, Monthly and Yearly .
I would like to add ,cancel and edit the job using a web page where user can schedule the job by providing periodic type, repeated frequency (measure of interval for ex: 5 minute, 5 hour , 5 days,2 week,2 month etc) and start date and end date.

Regards
Bruce

@LaszloKoller
Copy link
Contributor

Bruce,

Thank you for participating in the Revalee discussion.

Please keep in mind that Revalee calls back a URL at a specific date & time: no more, no less. This allows a consumer of the Revalee Service to develop a "task", that is, the processing work associated with the requested URL, which is as simple or as complicated as required. For recurring callbacks, let the application handling the called back URL do the work for you. Consider a task that needs to be triggered at 4:00 AM on the 5th of every month. In such an instance, you would schedule a daily recurring callback with Revalee. Every day at 4:00 AM, your web application would be called by Revalee. Since your application is designed to handle all of the actual processing work (remember: Revalee only calls back a URL at a set date & time), you would include a simple conditional that would evaluate today's date, à la "Is today the 5th? If so, proceed; if not, quit."

Some of Revalee's strengths include the ability to schedule thousands of callbacks ahead of time as well as the ability to "wake up" when a scheduled callback needs to be executed. You could schedule a callback months or years in advance and Revalee would remain dormant, including durability through computer reboots, until the moment the callback needed to be triggered. Also, keep in mind that all of these features are completely separate from your web hosting environment. Revalee does not depend on IIS, Apache, or any other web hosting environment in any way.

The current design paradigm for Revalee is to provide Revalee Service consumers with the tools necessary to architect & develop solutions that fit their specific application's needs. The Revalee API includes methods like, ScheduleCallback() and CancelCallback(), which allow application designers to include as much (or as little, including none) scheduled callback management as their application requires.

In the meantime, if you require a scheduling utility that does include a pre-built management console, then you may want to consider evaluating Quartz.NET and the application ecosystem developed around it. If Revalee's design paradigm changes to include job scheduling in the future, then we will naturally revisit the features you requested here.

Regards,
The Revalee Team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants