Kevin Dangoor wrote:
To realistically put multiple end-user-visible applications in one
process you need some styling system (for services/APIs it's not
really important). There's two layers where this can happen:
* You can use a filter that applies styling to unstyled content.
Deliverance, which I'm working on, does this (http://openplans.org/
projects/deliverance). We're going to add a few features here and
there, but the project is pretty far along. It works as WSGI
middleware, and we've built an HTTP proxy from that which is what
we're actually using in deployment.
There is another solution here. Genshi's match templates can be used
just like XSLT to add styling around the output that's coming from the
inside.
True; anything XSLT-like fits the bill. A lot of what we're doing with
Deliverance is aimed at making themable sites for untrusted users
(MySpace-like); it's not terribly constraining to do so, but some of the
choices we make are based on that. That will probably end up being a
distinction between something written in Genshi and Deliverance.
The actual filtering logic for Deliverance has mostly been extracted
into WSGIFilter, though I think I've probably broken that at the moment
because I've done a major refactoring of WSGIRemote (which is in the
process of a rename).
Proxying from Python to another service is also a useful way to apply
this kind of styling to non-Python content; this is actually going to be
our first deployment strategy with Deliverance. This just uses
paste.proxy, and some glue code in WSGIFilter.proxyapp
--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
