Re: [web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

Hello Anthony, Is that normal that multiples sessions files get created in case of FS sessions?? Regards Richard On Wed, Apr 4, 2018 at 3:09 PM, Anthony wrote: > One potential downside of db sessions is that you can have race > conditions, as the session record does not

Re: [web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

One potential downside of db sessions is that you can have race conditions, as the session record does not get locked (unless something has changed). On the plus side, if you have multiple Ajax requests that all just need to read (but not write to) the session, they can be handled

Re: [web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

DB sessions are so much more convenient... you only need one connection, not need to access remote server or sudo password etc... Walk the extra mile and set a cron job for session2trash clean up and you now have one less thing to check for... Depending on your workload, you don't have to do

Re: [web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

Well, I will stick with DB sessions from now. Thanks! -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are

Re: [web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

About session clean up, I recently set it in place (finally) and I can assure you that db sessions get cleared as expected. About the FS sessions, I can say for sure but maybe it faster to just create another file than search the exsting file, then append or rewrite part of it... Finally it

[web2py] Confused about web2py sessions handling in the filesystem, versus the db handling.

Hi. I'm experimenting for the first time (but I'm quite a bit old using this amazing framework :)) storing sessions in the DB instead the filesystem, as I always did. I'm monitoring those two behaviours and somehow it feels (at least for me) that the DB session handling is far away more