Thanks, Definitely makes sense for it to be cached, but I expected it to be re-scanned within an hour or so, which didn't seem to happen.
So if you're using a memcache cluster (I'm not...) does everything get cached to memcached - I'd assumed it would only cache the actual gadgets etc, and make sure that files like that were available locally in-RAM (assuming you're using mod-php). I'm proxying to the gadget server behind a front-end server with fairly heavy caching anyway, so knowing how long changes will take to be replicated through to users is becoming a bit of a headache. Tim On Fri, 2008-11-07 at 20:31 +0100, Chris Chabot wrote: > The parsing of the features is one of the most expensive things > php-shindig does in a request, thats why the result of it is cached. > > Flushing the cache is as simple as > # rm -rf /tmp/shindig > on a *nix machine > > or if your using memcache, simple restart that.. or if your on > windows, it's somewhere in C:\Documents And Settings\<user>\Temporary > Files (don't hold me to the last one, i'm not much of a windows nut, > but it's in some temp directory somewhere) >
