perhaps, instead of using the users' method directly, create a logout
handler where you perform the necessary operations before fowarding to
the logout uri.
the tricky part is keeping track of the original uri. the way i do it,
is to pass it as a request argument. you could maybe subclass the
request handler, with a logout method. such as:
def logout(self, uri=None):
<check that there really is a user logged in
if uri is None: uri = self.request.uri #not sure this part works..
<del session and stuff..>
self.redirect(user.logout(uri))
..
im not 100% sure about this since im just typing this on my phone 50ft
underground in a speeding subway train with nothing to refer to, but
you should get the idea.
when i get home ill see what code i use exactly.. ;)
ps i actually just missed my stop! lol.. damn you google!! (shakes fist)
Sent from my iPhone
On 09-03-04, at 00:01, OliWeiD <oliver.weimar.dr...@googlemail.com>
wrote:
>
> Hi everybody,
>
> due to security reasons and for efficiency some sort of logout handler
> is needed.
> That means, when the user is clicking on the created logout link
> (users.create_logout_url)
> During that logout I want to delete a session cookie and delete the
> memcache entries for that user.
>
> Any idea?
> Kind Regards
> Oliver W-D.
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
