What happens to Oauth 2.0 sessions during deployment?

[Vladimir S]

Hi,

I have a simple python 2.7 webapp2 site in GAE which makes users authenticate via Oauth 2.0 to grab their Google+ full name to display on a hello world page. Would users of such site get errors or notice issues during a traffic relocation (silent deployment) to a new version with changed hello world message? The URL is kept the same but I still don't know if the Oauth tokens will remain valid. Will memcache have any part of this switch or is it reset after deployment?

Thanks

PS. I posted this on SO earlier but I think the question is more relevant here.

[Adam (Cloud Platform Support)]

Memcache is a shared service which uses memory, but this is independent of your instance's local memory. It will not get flushed, and neither will Datastore data, where OAuth tokens are typically persisted. In practice, users will not notice a traffic relocation (barring any application issues with the new version) much the same as they would not notice traffic being served from a different instance clone.