Marijn For what use-case do you want to flush the cache? We haven't added the ability for gadget developers/end-users to do this on demand but there has been some dicussion of this on the spec list. Your observation about nocache=1 is correct and is implemented that way to allow the gadget to continue to be served if the HTTP request for the gadget spec fails as we can still use the one on the cache in the interim and forcibly flushing it would have prevented this.
-Louis On Wed, Aug 6, 2008 at 6:53 AM, Marijn Speelman <[EMAIL PROTECTED]> wrote: > Is there a way to refresh the http response cache (which caches manifest > files, rewritten content, internal js feature files, proxy requests), > without restarting Shindig? Or what could be the best place to build this > in? > > I don't think nocache=1 works for refreshing everything. For instance, when > using nocache=1 the in-memory GadgetSpec cache is refreshed, but as far as I > can see the entry in the http response cache is not (it's bypassed > completely). Could this theoretically result in two different versions of > same gadgetspec? > > Thanks, > > Marijn >
