So regarding WSGIKit and Webware, how do you think we should proceed as far as the code base and development goes? Should we try to move Webware over to use WSGI, should we develop them in parallel? It seems to me we should at least put them in the same version control system. I prefer Subversion myself, but Sourceforge is very dependable.
It's hard to say how development should continue. It depends a lot on what other people think, I guess. Right now WSGIKit shares very little (no?) code with Webware, somewhat intentionally. Some of the code could be moved over -- for instance, Webware handles sessions more efficiently than WSGIKit (which loads and saves pickles for every request). And Webware has better error reporting (WSGIKit just has cgitb). I'm open to any suggestions about how to procede.
I've come to quite prefer Subversion to CVS. I could move WSGIKit over to svn://w4py.org
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Webware-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/webware-discuss
