2009/3/5 mdipierro <[email protected]>: > > I am not opposing, just asking... isnt this file already too fat?
I agree it is already quite big. But until the auth stuff is documented in the regular documentation I was not opposed to your decision to add all those comments. > Why include memcaching on GAE and not ram caching on non-GAE? 1. On GAE if one wants to use sessions, something has to be done expicitely. Either store it in BigTable, or, which I just learned two days ago, store it in Google Memcache, which is IMO a superior solution, since it does not lead to piling up all those sessions in BigTable. And since access to BigTable is under quota, it seems to be another reason to have sessions stored in Memcache. 2. On non-GAE sessions work out of the box, so it is not mandatory to tweak session handling. Memcache on non-GAE requires setting up a Memcached server, so it would not be enough to just uncomment a few lines in db.py. And caching the sessions in RAM is IMO currently not possible with web2py. Am I wrong? Kind regards, Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
