• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTimer replacement?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTimer replacement?


  • Subject: Re: NSTimer replacement?
  • From: Robert Walker <email@hidden>
  • Date: Wed, 9 May 2007 12:54:04 -0400

Johann,

I think that would be fine if you have a fixed schedule that doesn't change over long periods of time so you could set it manually. The biggest drawback I see in using cron/launchd is that it is way more difficult to change these schedules by your WO apps in response to an user action (file access to sensitive files, need to parse and change the config files, file permissions). It could get even more complex if you deploy on several servers with failover in mind. Then you had to be carefull where to put in the cron/launchd config files to not having more than one server running the system schedule. Putting that information in a db alleviates the problem when using db clustering.

Yes, you are correct.  I use this in simple cases where I do some periodic processing on a fixed schedule.  For more complex, or dynamic, scheduling I use the cron/curl to simply trigger the system to periodically read the schedules configured in the database in a similar fashion to Kieran's solution.

On May 9, 2007, at 10:47 AM, Johann Werner wrote:


Am 09.05.2007 um 16:34 schrieb Robert Walker:

Keiran,

I do something very similar to this except I typically use an external scheduler such as cron or launchd, which calls direct actions using curl to handle each task.  This way the scheduling databases becomes a simple crontab or launchd style schedule.

I think that would be fine if you have a fixed schedule that doesn't change over long periods of time so you could set it manually. The biggest drawback I see in using cron/launchd is that it is way more difficult to change these schedules by your WO apps in response to an user action (file access to sensitive files, need to parse and change the config files, file permissions). It could get even more complex if you deploy on several servers with failover in mind. Then you had to be carefull where to put in the cron/launchd config files to not having more than one server running the system schedule. Putting that information in a db alleviates the problem when using db clustering.

jw

--
Robert Walker
email@hidden



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: NSTimer replacement?
      • From: "Ted Archibald" <email@hidden>
References: 
 >NSTimer replacement? (From: Johann Werner <email@hidden>)
 >Re: NSTimer replacement? (From: Kieran Kelleher <email@hidden>)
 >Re: NSTimer replacement? (From: Robert Walker <email@hidden>)
 >Re: NSTimer replacement? (From: Johann Werner <email@hidden>)

  • Prev by Date: Re: Getting a project started right
  • Next by Date: Re: Merits of D2JC (was: user obstacles to WOLips adoption (was: Apple's Support of WebObjects))
  • Previous by thread: Re: NSTimer replacement?
  • Next by thread: Re: NSTimer replacement?
  • Index(es):
    • Date
    • Thread