On Tue, May 5, 2009 at 3:05 PM, Ivan Arar <ivan.a...@gmail.com> wrote:
> Hey, > > Sorry for posting to wrong group. Hope I hit the right one now. > No worries, having an opensocial-containers group does tend to lead people down that path more often; But as far as shindig developers and support goes, you'll find a lot more of it here :) Looks like forced-refresh worked! Although I find this very strange because > I refreshed the page numerous time before. > Shindig tries to cache, and cache and cache some more ... when your running in full production and getting tens to thousands of hits a second, well it goes a long way to helping the gadget's servers to survive the traffic; Also the web browser is told to cache things as much and long as possible, so sometimes if there were timeouts or errors in the curl module, it can cache an invalid document. force-refresh in the web browser has 2 functions, first of all it forces it to re-download the image even if the max-age cache control told it not too for that duration, and it also sends a pragma: no-cache to the server that php-shindig honors (it will re-fetch the document even if it has a cached version of that file), so it's a good way to double check. While developing these things can sometimes occur, the easiest way to make sure you start out with a clean situation is by cleaning out the cache directory (the default config is set to use file based caching, which it stores in the /tmp/shindig directory), so doing a rm -rf /tmp/shindig gives you a completely clean start again.. combine that with a force-refresh in the web browser (to make sure it won't use it's browsers cache), and you have a complete reset situation again. > Anyway, my remote Shindig server is working now but localy neither > force-refresh nor 30 sec curl timeout worked. > Possibly your behind a proxy server? If so there's a config for that too in config/container.php: // If your development server is behind a proxy, enter the proxy details here in 'proxy.host.com:port' format. 'proxy' => '', > Yes, I already took Partuza into my hands and majority of my work for now > is based on it. Thanks for wroting that J > Glad to hear it's useful :) Good luck and let us know how things go! -- Chris
