-winston
On Dec 29, 2004, at 2:09 PM, Ian Bicking wrote:
While we're talking about improvements, I might re-note the existance of WSGIKit: http://svn.colorstudy.com/trunk/WSGIKit/_________________________________________
I'm personally convinced that this should be the future of Webware (and, in a general architectural sense, Python web programming as a whole). It offers a few current advantages over Webware:
* Deployment with different servers.
* Simple CGI and multiprocess deployment (e.g., embedding Webware in mod_python).
* Some framework neutrality; in time it should be possible to embed other frameworks under Webware, and vice versa. (Well, you can do it now, there just aren't that many other frameworks to embed.)
* Decoupled functionality. Dependencies between components are quite minimal.
* Easier testability. In part because of the decoupled functions, but also because WSGI provides a spec that makes fake requests very easy to construct.
* Easier application testability (functional tests), again because WSGI requests are easy to simulate.
* Distutils-installable.
* Removes some of the installation cruft we have now.
* Mostly backward-compatible. There are some missing corners of the Webware API, but that can be fixed. The whole MakeAppWorkDir thing goes away (for better or worse), and Contexts disappear. But I believe most applications should be able to run under it without modification, or only with small modifications.
* It uses spaces not tabs ;)
Missing parts:
* No PSP. Shouldn't be that hard, but I don't use it so I haven't ported it. The hooks are there (urlparser.URLParser.register_constructor).
* No configuration, except by passing in keyword arguments to various constructors. I have a config-file parser that I haven't started using, but should allow lots of cool things. Configuration won't be backward-compatible. This is the thing at the top of my list for WSGIKit.
* Some parts have sub-optimal implementations, like the session handler. It works, but it may be slow.
Certainly WSGIKit isn't ready to replace the main Webware at this time. But I think it could reach that point reasonably quickly, because the architecture is easier to test. Progress so far has been quite good -- which isn't to say it's developed super-fast, but I haven't put a ton of time into it either.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss
winston wolff - (646) 827-2242 - http://www.stratolab.com - learning by creating
