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 wrote:
> My concern is that the client may make multiple requests for a
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. Ther
> Perhaps this is more a question about application design then directly about
> Memcached.
>
> I have a very large and somewhat slow data fetch from a back-end service.
> The client doesn't need all the data at the same time so the plan is to split
> it up into parts and save into Memcached to
Perhaps this is more a question about application design then directly about
Memcached.
I have a very large and somewhat slow data fetch from a back-end service.
The client doesn't need all the data at the same time so the plan is to
split it up into parts and save into Memcached to be fetched as
