How about writing or updating a memcache entry for each user and specifying a lifetime, each time they view a page.
The use these entries to see if a user is logged in. You will need datastore entities representing each user. The trick will be doing an efficient intersection between all the user entities and those that are have an entry in memcache, Just an idea T On Apr 10, 10:13 pm, slmnhq <[email protected]> wrote: > Hi, > > I am trying to build a community website which has a very familiar > pattern: > - it displays the list of all users that are currently logged-in > - it allows each user to filter the above list by some criteria (eg: > geo-location, age, etc). > > I've never done this before, so I was hoping somebody could point me > to articles that talk about the ins-and-outs of these features. Also, > I want to understand how the DB and Memcache will factor into this. > > One issue that is completely stumping me is when a user may be logged > in, but has been inactive for a long enough period of time that he/she > is effectively logged-out and should be removed from the list. > > I will appreciate any ideas. > > Thanks, > Salman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
