Nope, I filter off the timestamp for the method that goes through and
cleans up stale sessions.
def _clean_old_sessions(self):
"""
Delete expired sessions from the datastore.
This is only called for CLEAN_CHECK_PERCENT percent of
requests because
it could be rather intensive.
"""
duration =
datetime.timedelta(seconds=self.session_expire_time)
session_age = datetime.datetime.now() - duration
query = _AppEngineUtilities_Session.all()
query.filter('last_activity <', session_age)
results = query.fetch(1000)
for result in results:
data_query = _AppEngineUtilities_SessionData.all()
query.filter('session', result)
data_results = data_query.fetch(1000)
for data_result in data_results:
data_result.delete()
memcache.delete('sid-'+str(result.key()))
result.delete()
On Aug 28, 12:31 pm, javaDinosaur <[EMAIL PROTECTED]> wrote:
> Got it, just tuned into your thought processes... there is no ssl
> hence the sniffing risk. All my preconceived ideas on this subject are
> based on the assumption of SSL encrypting data on the wire.
>
> The GAE Team has 3 more months to announce SSL otherwise I will be
> forced to shift my development efforts onto another Cloud platform.
>
> Could the timestamp be stored in a text field to avoid the Datastore
> doing extra index updates on each of your session entity puts?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
