Hi Barry,
The way the sandbox currently works is that the same cached
version is served to all users who are not specifying &bpc=1 in their
querystring. This is why you can put &bpc=1 on a URL, view the
updated version, and then remove &bpc=1 to see the older version
again. Currently, this cache expires after about an hour, so if you
make a change to your application spec, then your users should all be
viewing the updated spec after about an hour.
If expiring the cache is still something you would like to have,
then please add it to the feature requests page:
http://groups.google.com/group/opensocial/web/opensocial-feature-requests
Hope this helps,
~Arne
On Dec 6, 2:27 pm, Barry Welch <[EMAIL PROTECTED]> wrote:
> Yeah, but, when we deploy to production and the Spec XML is cached...
> how long does this caching last, and will it expire? Can I manually
> expire the cache for this? Because, lets say my app gets 500 users and
> I find a bug or want to add a new feature and so I change the code.
> How do I make sure that all my users are getting served latest app
> spec?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Orkut Discussion" group.
To post to this group, send email to opensocial-orkut@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
