Hey guys, Maybe I'm just ignorant (highly probable), but I'm really having a hard time keeping up with the "configuration" emails, especially when each of you is using slightly different definitions and trying to reach slightly different goals. Please forgive me for coming out and stating this.
With the number of participants in the conversations, it doesn't seem like we're making a huge amount of progress, although perhaps I should shut up and be patient. In the meantime, I'd like to propose that we framework authors try to start sharing our backend session code. Let's just create a library like Apache::Session <http://directory.fsf.org/webauth/misc/apache-session.html>. As much as possible, I think we can make it framework agnostic, relying on the framework itself to respond to callbacks for doing things like setting session cookies and creating a database cursor. Just like with WSGI, the frameworks need not change their external APIs. Let's keep it simple and just make it a library. (I'm not sure the Twisted folks can participate because things on the Twisted side are always so different, but hopefully I'm wrong.) In any case, it's just a proposal to try to share more code. If I can get two other major frameworks to say they'll commit to working with me and using/contributing to the library, I'll start the endeavor and give them CVS commit rights. We need not write much new code. I'd like to reuse code that each of us already has. This will have the benefit of a lot of peer review. Perhaps this will make for a slightly better (Python Web) world :-D Best Regards, -jj -- I have decided to switch to Gmail, but messages to my Yahoo account will still get through. _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
