Hi Martyn, On Wed, Aug 5, 2009 at 9:48 AM, Martyn<[email protected]> wrote: > > Hi there, > > In testing I have noted latency in user identity management when I > sign in and out as different account users. > > 1) I sign in as user A - application recognises me as user A > 2) I sign out - application still recognises me as User A > 3) I sign in as user B - applicaiton recognises me as user A > 4) sometime later (around a minute) application recognises me as user > B > > I understand how this could happen, based on caching for performance, > but should it?
If you're caching responses, there's nothing any of the rest of the infrastructure can do about it. You need to use a caching strategy that can cope with users logging out, such as using etags. Have you checked to see if this _is_ a caching issue? Does your App Engine app see requests from the newly logged-out user, or are they entirely served from the cache? Are you using the Users API, or your own session management? How are you logging out of the app? > > ...and I'm still concerned about insert performance, seems like 120ms > is the best I can hope for (single row, no indexed properies, Blob of > around 1k). This seems high. Have you experimented with entities with different numbers of properties and entity sizes? -Nick Johnson > > - Martyn > > > -- Nick Johnson, Developer Programs Engineer, App Engine --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
