On Oct 7, 12:24 pm, Michele Simionato <[EMAIL PROTECTED]> wrote: > Here we disagree: I think that a programmer should know what he > is using.
My point was that they should not *need* to know. Too much information can be detrimental. > > Where is the session data stored: in memory, files, database and so > > on. > > Of course Beaker has all these features Well their main page does not say anything about database based storage: http://beaker.groovie.org/ but then a Pylons wiki says it does, but I could not find any information on out how to set up beaker with a database ... truth to be told I was just curious of how they would go about integrating a database and still keep it "pluggable". Because it would either need to know about the way the server handles the database connections (which makes it application specific) or it has to create new database connections in which case it would be duplicating the functionality leading to all kinds of headaches. So there, even a simple requirement exposes the fallacy of building anything complex out of "pluggable" components. i. -- http://mail.python.org/mailman/listinfo/python-list
