For example:
Cached:
http://sandbox.orkut.com/Application.aspx?uid=x&appId=x
Not cached:
http://sandbox.orkut.com/Application.aspx?uid=x&appId=x&bpc=1
Please note that you do not append bpc=1 to the url of the gadget you
install.
~Arne
On Nov 3, 10:32 am, "Arne Roomann-Kurrik (Google)"
On Nov 3, 10:32 pm, "Arne Roomann-Kurrik (Google)"
if sandbox for development
then disable cache = true
why the orkut sandbox does not have that by default?
- bala
http://beyondwork.wordpress.com
On Nov 3, 10:32 pm, "Arne Roomann-Kurrik (Google)"
<api.kur...@google.com> wrote:
On Nov 3, 10:32 am, "Arne Roomann-Kurrik (Google)"
Greg Magarshak
On Nov 3, 12:32 pm, "Arne Roomann-Kurrik (Google)"
http://www.tricks4fun.com/orkut-sandbox-permanent-no-cache/
On Nov 3, 10:32 pm, "Arne Roomann-Kurrik (Google)"
Greg
These are valid concerns, and we're aware that gadget developers
don't want to get stuck between API versions and caching. For the
first issue, the cache lifespan is only an hour, so users with older
versions of the gadget will only be out of sync for a relatively short
period of time. Secondly, you'll notice that the <Require
feature="opensocial-0.5" /> contains a version number. The plan is to
release a higher version API while still supporting a lower version
number for a short period of time, so that developers are able to port
their apps while minimizing downtime due to breaking changes in the
API. We won't be able to guarantee this for all changes (if the
underlying infrastructure changes, for example) but we'll certainly be
working hard to minimize the amount of pain that such changes will
bring.
~Arne
Why can't caching just be turned off in the sandbox for everyone by
default?
Even so, caching the remote data may be an additional problem...
The server I'm being routed to is: un64mq1e-a.modules.com
Ron
Why not flush the cache whenever there's a new api release is pushed
out?
(Dan)
Yeah, for me also it doesn't pick up any changes in the XML file. Is
there another OpenSocial sandbox we can use te develop on?
--
Alper
Are you using the refreshInterval parameter for your IG_Fetch
calls?
>From http://code.google.com/apis/gadgets/docs/remote-content.html#Params
:
// Disable caching completely and fetch fresh content every time
-- !! Try to avoid using this !!
_IG_FetchContent("http://news.google.com/?output=rss", callback,
{ refreshInterval: 0 });
This should be fine for development purposes.
I'm seeing a lot of cases where people are using &bpc=1 but their
browser continues to cache the old code. If you're still seeing old
data, can you try disabling your browser cache and seeing if the
problem goes away?
~Arne
That would make sense. I'll bring it up with the team doing the
pushes.
~Arne
On Nov 10, 6:07 am, "Daniel C. Silverstein (cubes)" <cu...@slide.com>
wrote: