[Skunkweb-list] SaTiMoL (skunk4)
Brought to you by:
drew_csillag,
smulloni
From: Jacob S. <smu...@sm...> - 2007-09-04 19:55:01
|
Hi -- Three years ago I did some work on what I thought would turn into SkunkWeb 4, but I had a third child at the same time and couldn't find time to keep working on it, although I've been using one part of it (skunk.cache) in production for a couple of years now. However, in the last few weeks I've been able to get back to it, and I'm now a few days work away from an alpha release. The code is in google-hosted subversion at http://code.google.com/p/satimol/ =20 ("satimol" is a nonsense word based on "STML". It sounds vaguely pharmaceutical -- perhaps an emetic.) In keeping with the spirit of WSGI, what I've done is really more of a set of libraries than a monolithic application. I have not been particularly interested in maintaining backwards compatibility, but I have been interested -- indeed, it is my primary interest -- in making sure that old SkunkWeb applications are relatively easy to port to the new framework, at least easy enough that I am willing to do it myself. It should also be easy to run SkunkWeb applications inside other WSGI applications/containers, to run other WSGI applications within SkunkWeb, and to use the skunk libraries inside WSGI applications that are tightly coupled to other frameworks (you should be able to use STML in a framework that supports Buffet, for instance). At the same time, you don't need to buy into those larger frameworks; skunk will run fine by itself. =20 I have taken advantage of other libraries which I particularly like. I've been using Routes for a couple of years, and I'm using that for dispatching by default (although you can use something else if you want). I also was very pleased by Ian Bicking's recent WebOb library, and I'm using its Request and Response objects instead of a CONNECTION object; it is fairly pervasive in the skunk.web package, so that's a hard dependency (but not on STML itself for the most part). =20 For now, there is no server container -- use flup, cherrypy.wsgiserver,=20 wsgiref, or paste.httpserver. That, and mod_skunkweb support, will come later. My main priorities between now and the first alpha release will be to document what I've done, and fix the first dozen or so glaring errors that crop up. =20 As there is no manual yet, the "examples" directory may be the best place to start to get an idea of what is going on. Cheers, js --=20 Jacob Smullyan |