Yeah, I say either go with Gearman or else have backend processes that
generate the data and write it to the cache instead of generating it within
the context of a client request.
On Sun, Sep 26, 2010 at 12:44 PM, Brian Moon br...@moonspot.net wrote:
My concern is that the client may make multiple requests for additional
parts at the same time triggering multiple (duplicate) re-fetches and saves.
Anyone have a similar situation? Would you recommend
use an atomic add with a short timeout as a lock?
It's discussed on the wiki a bit. There's the Ghetto lock with add, but
also things like gearman which can do request coalescing.
Gearman++
--
Brian.
http://brian.moonspot.net/
--
awl
