Yes Holger, I think that is right. I am using the web.xml security-constraint declaration, which is almost by definition implicit in the JVM deployment.
I confess to remaining confused over the precise method that the UserService uses to access logged in user. My suspicion is that it may use Memcache with some shortish Expiration Policy - perhaps keyed on user IP. This would explain the effects I see. Just a guess though. We'll have to find something else to talk about ;-) On 6 Aug, 10:56, Holger <[email protected]> wrote: > When testing my own apps different browsers did work, as my app works > with cookies, which are shared between different windows of the same > browser on the single machine but not shared between different > browsers. > > But maybe we have got a different concept. I see my app as main app > outside of the Google world, use Google just as external login > service, care myself for logout, dont offer a login link as long as > the user is logged in and don't care for further user actions in the > Google world. If my user logs out there, that's his fault not mine. > > And if I switch to native Django login, even the possiblity to use a > Google account instead of my apps accounts is dropped totally. > > Probably you follow another concept. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
