Hi Barry. Unfortunately, there is no way to manually flush the cached gadget XML outside of the Orkut sandbox, but I can see how this could be useful. I suggest that you file a request for this feature using the public issue tracker. A set of instructions detailing how to do this is available here:
http://code.google.com/p/opensocial-resources/wiki/IssuesTab?tm=3 In the meantime, you may consider deprecating your API functions instead of removing them altogether, assuming this is feasible. If you can add a version tag to each of your functions, at least until your API is fully mature, you can continue to support both API calls. This way you can be sure that all users of your application can have a good user experience, regardless of whether the cache has been flushed. I hope this helps. Cheers! - Jason On Feb 14, 2:30 pm, Barry Welch <[EMAIL PROTECTED]> wrote: > Our team plans on doing constant minor updates to our spec and our > backend API in the early days of the 'live' deploy. Because our > javascript client app relies on a backend server, we never want client > code to be out of sync with the backend code (like changing parameters > for making calls, etc), How can we be sure that when each user opens > our app, they are getting the latest version of the spec so that we > can maintain that synchronization? It seems like there should be a way > for a developer/admin to manually expire the xml spec cache when we > make changes so we can ensure a seamless update. Is there such a thing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Orkut Developer Forum" 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-orkut?hl=en -~----------~----~----~----~------~----~------~--~---
