Jeff Watkins, el domingo 8 de enero a las 14:11 me escribiste: > >What about sessions prevents them from being used in a clustered app? > > Principally, sessions are stored in ram (for speed) or in a DB for > clustering support. Unfortunately, CherryPy's sessions only support > PostgreSQL, which means they're not a valid solution for TurboGears.
So I guess if there's a problem in CharryPy, the better place to fix it is in CherryPy, not in TG. > Furthermore, one of the design goals I was given was to avoid using > sessions. And why is that? > >And since most web applications are not clusters why force this on > >them? > > If you're really worried about scalability (like enterprise apps) you > *will* be deploying in a clustered environment. That's what makes it > an enterprise-class solution. Without clustering you're dead when one > machine goes down or gets thrashed by a runaway thread. I still think sessions is the abstraction layer where this belong. If it's broken, let's fix it instead of reinventing the wheel... -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ .------------------------------------------------------------------------, \ GPG: 5F5A8D05 // F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05 / '--------------------------------------------------------------------' El techo de mi cuarto lleno de planetas Y mi mente es un planeta más Donde vivo yo y nadie podrá entrar Jamás
