Arne - it's cool to be able to not cache the gadget, but this brings
up a problem which I mentioned in another thread ("Unofficial bugs").
If gadgets are cached AND the underlying API implementation changes
(which, if experience with facebook taught us anything, is very
possible), it will be a big problem. If the container changes its
implementation, all the cached apps would break. At which point can
app developers "fix" and "adapt" their applications then? Perhaps, if
you really will cache javascript, there should be some revision number
for the container's implementation. When it changes, the app
developers have a chance to upload a script with the new revision
number, so that (potentially) millions of users aren't stuck having to
re-add the application.Greg On Nov 4, 4:40 am, Sahil <[EMAIL PROTECTED]> wrote: > I have created a Greasemonkey script for firefox, which will append > &bpc=1 automatically to the application pages. > > http://www.tricks4fun.com/orkut-sandbox-permanent-no-cache/ > > On Nov 3, 10:32 pm, "Arne Roomann-Kurrik (Google)" > > <[EMAIL PROTECTED]> wrote: > > Orkut's sandbox caches your gadget to improve latency. This is > > undesirable during development, so to bypass caching on a given Orkut > > page, please append &bpc=1 to the URL of the page itself: > > > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
