Feature-wise, web2py is pretty complete. I think the next milestones of web2py should be on performance and scalability; (web2py is reaching 2.0 sooner or later, right?)
I would like to see stronger built-in support for smart caching and load balancing (distributing work across different servers). I have a simple idea about smart caching (I don't know if it works or not). As web2py controls database access via the DAL, we can update the cache only when the database is updated. If the database is not modified, there is no reason to refresh the cache. Right? To be safe you can set a minimum time (e.g. 5 minutes cache refresh), "just in case". On Mar 15, 2:35 am, Tom Atkins <minkto...@gmail.com> wrote: > Just looking at CubicWeb via the link given on Reddit. Looks like an > interesting project - amazing what's out there that I've never heard of! > > This blog post: > > http://www.cubicweb.org/blogentry/1484253 > > describes an interesting way of using multi core processors to load balance > and solves session caching via squid. Might this be a useful approach to > use for scaling web2py?
