[Chicago] appengine session locking

[Massimo Di Pierro]

this is what the source code of Beaker says:

     # datastore does its own locking (or does it? who knows).   
override our
     # own stuff
     def do_acquire_read_lock(self): pass
     def do_release_read_lock(self): pass
     def do_acquire_write_lock(self, wait = True): return True
     def do_release_write_lock(self): pass

I believe the datastore does not do its own locking. So Beaker does  
not lock sessions.

Massimo

Cookie-only sessions to remove the need for a db or file backend  
(ideal for clustered systems)

On May 12, 2008, at 12:30 PM, Kumar McMillan wrote:

> On Mon, May 12, 2008 at 12:17 PM, Massimo Di Pierro
> <mdipierro at cs.depaul.edu> wrote:
>> Does anybody have experience with session locking on appengine?
>>  The appengine does not have an update....where command so how do  
>> people
>> lock sessions stored in bigtables?
>
> you could poke around the trunk of Beaker:
> https://www.knowledgetap.com/hg/beaker/archive/tip.tar.gz  
> (beaker.ext.google)
> http://wiki.pylonshq.com/display/beaker/Home
>
> Beaker is a session/cache lib for Pylons and support for appengine was
> added recently.
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20080512/9da0751a/attachment.htm>