On 24 Feb 2009, at 16:35, Nicholas Leippe wrote:
Just add a timestamp and a lock. If a page request finds the timestamp is too old, attempt to grab the lock and then do the refresh queries and update the timestamp. If it fails at the lock, another page got it and did it, so poll until the timestamp is changed and then go. (If you really need speed you could implement the timestamp test to block until ready.)
While I do not have much experience with locking database records, how will that eliminate the hits to the database? Is a hit that encounters a lock and then stops significantly less overhead than a hit that retrieves a record?
smime.p7s
Description: S/MIME cryptographic signature
/* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
