On 17 Lis, 16:09, A.TNG <
tang.j...@gmail.com> wrote:
Or you can try my
http://schedulerservice.appspot.com/
Main difference is that gaeutilities Cron runs inside your own app
inside requests initiated by regular (human) clients. Cron tasks will
not fire if there are no viewers, but generally every useful site has
at least some page views per day, so that shouldn't be a big problem.
On the other hand, Scheduler Service uses agents that call your url
from external hosts, so the whole thing doesn't depend on human
guests. But those external agents run on my servers, not Google's
ones, so if I were you I woudn't expect them to be that reliable
(altough me being me - I do expect them do be reliable, because I
simply trust myself ;). Also, with gaeutilities you can define any
number of tasks that will execute as often as you like as long as
there are human-initiated page views on your site. Scheduler Service
let's you define only a few schedulers that run at most 1 time per
hour.
Maybe the best thing would be to mix two technologies in new sites,
that is - run Cron tasks from both human and schedulerservice urls and
after your site (hopefully) gets some audience, drop schedulerservice
part?
Hope that helps.
Regards
Maciej