On Friday, April 12, 2013 2:49:15 PM UTC-5, Simon Knott wrote: > It could be completely unrelated to the User data model - if they are > storing any other serialized objects in the session which have had their > structure updated between v15 and v17, then when the session object gets > deserialized from the datastore/memcache, it will also have the same > symptoms. > > The suggested fixes would still resolve the issue as well. > > Cheers, > Simon > > +1.
Let me change what I wrote: Pretty much anything that has been serialized could be breaking, if you changed the class between v15 and v17. I bet it's the user model, because login is breaking and not anything else, but it could be a lot of other things. You still need to implement a way to version client session IDs; storing it in the User model or the session attribute, both are fine. ----------------- -Vinny P Technology & Media Advisor Chicago, IL @GOV on AppDotNet: https://alpha.app.net/gov -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
