Hi Barry, That would be a good feature request to file in the tracker here: http://code.google.com/p/opensocial-resources/issues/list
The caching infrastructure is pretty distributed, though. It would be pretty hard to ensure that all users see the same version of your gadget at the same time. For this reason, try to structure your application with a schema ID number stored at each client. New versions of the app should update this number, and your backend should ideally be able to cope with a couple different schemas at once. ~Arne On Thu, Feb 14, 2008 at 1:06 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 our 'live' deploy. How can we be sure > each user that adds our app is seeing the latest and not the cached > version of the spec. Seems like there should be a way to expire the > xml spec cache when we make changes. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
