Webcron: Difference between revisions

Revision as of 19:36, 27 September 2017

Revision as of 23:55, 27 September 2017

Line 11:

A webcron solution is made up of two pieces. The first piece is a script that will execute the tasks that resides somewhere accessible via a [[URL]]. The second piece is to use a scheduling provider that contacts the URL of the script at regular intervals.

Before setting up a schedule with a scheduling provider, a user must set up a script that runs on the web server. Most{{which|date=December 2010}} web hosts have restrictions on the length of time a single instance of a script may execute. Many{{which|date=December 2010}} web hosts also have limitations on [[CPU]] and [[RAM]] resource usage. Users of webcron solutions on [[shared hosting]]<ref>{{Cite web|url=https://www.webhostingology.com/topten/shared-hosting/|title=The Best Shared Hosting Companies 2017|website=www.webhostingology.com|language=en|access-date=2017-09-27}}</ref> providers must be careful to not repeatedly exceed their web host's limitations so as to not get kicked off. A script that runs a long time must take into account that it may be terminated at any point by a web server process. Users may implement a [[state machine]], which allows the script to operate across multiple invocations and run within the limitations imposed by a web host.<ref name="WebCronDoc" />{{psc|date=December 2010}}

== Scheduling Providers ==