This is an example -- I think -- where web2py still needs to be proven in terms of scalability.
Yes, sessions can be stored in database, turned off in specific functions, and regularly deleted. But I still think that there should be a better systematic way of handling sessions in heavy applications. I think the current set up is not effective when you have large volume of users, which suddenly builds up many sessions. Small things like this don't matter much until things get large scaled. === To take web2py to the next level, I think Massimo might need to lay out milestones or visions to be achieved in future releases of web2py. On Nov 30, 6:07 pm, Stef Mientki <stef.mien...@gmail.com> wrote: > On 30-11-2010 21:08, VP wrote:> I think .NET and web2py are not competitors. > They are different ball > > games. When things scale large, everything is important. A small > > design issue might be magnified. I don't think web2py is proven yet, > > in terms of scalability. What web2py needs is at least one real > > example to show that it is scalable and what are the limits at the > > extreme. > > I'm not sure were session files are used for, > but isn't file access much slower than database access ? > > Can session files be turned of ? > > cheers, > Stef
