storage? yes. Performance? maybe. storing session in cookies has the big advantage to not require any kind of load balancer with sticky session for large deployments (i.e. from 20 web2py instances up), but at the added cost of unpacking and repacking the cookie at every request. Also, be sure that what you store in session fits the limitation of the cookie (4kb) . Turn on compression if you need more, but test carefully.
On Sunday, March 10, 2013 8:24:14 AM UTC+1, Jaime Sempere wrote: > > Hi, > > I have an application for facebook where I need to store some variables. > The application is like a little forum but with just one page and > everything is loaded via Ajax calls, so I need to store for example, the > user that is logged in, the page of the forum where he is right now... etc. > Now I am using 4 variables stored in sessions, I would like to know if this > practice is considered correct. > > Also, as sessions are stored in server side, I was thinking to use cookies > instead of sessions. Would this be better in terms of performance and > storage? If not I would like to keep using sessions, I found them easier to > handle, and I would avoid to rewrite the code. > > Thanks in advance > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
