[Chicago] web2py on appengine
Massimo Di Pierro
mdipierro at cs.depaul.edu
Tue Apr 22 14:28:55 CEST 2008
Only the disk based session will not work. You can use the google
api and save session on the database using the google api. something
def index(): # controller
# try retrieve from DB or create session object called
# body of the controller, use the session object
# save session object with name response.session_id
response.session_id=None # don't save this session on disk
The cookies and generation of the name response.session_id is automatic.
As soon as we port our ORM there will be an API for all of this.
On Apr 22, 2008, at 12:48 AM, Cosmin Stejerean wrote:
> i'll have to check it out. any chance of making sessions work
> (probably using the AppEngine data store as a backend)?
> - Cosmin
> On Mon, Apr 21, 2008 at 11:52 PM, Massimo Di Pierro
> <mdipierro at cs.depaul.edu> wrote:
>> Here is a version of web2py that works on appengine
>> if and only if....
>> 1) you do not use the web2py ORM, you can use the appengine one
>> 2) you do not use admin (since you cannot edit files)
>> 3) you do not use cache.disk (same reason as before)
>> 4) you do not use sessions (response.session_id=None)
>> 5) you do not bytecode compile applications
>> unzip web2py_for_appengine.zip
>> then visit: http://127.0.0.1:8080/welcome
>> While this works on the appengine we are running tests to make
>> sure we did
>> not break anything else on "other" platforms.
>> We are also working on porting the web2py ORM to the appengine
>> which should
>> be trivial. As soon as this is done this will go in trunk.
>> Chicago mailing list
>> Chicago at python.org
> Cosmin Stejerean
> Chicago mailing list
> Chicago at python.org
More information about the Chicago