Hi guys. Sorry I missed the IRC conversation today. I was just reading the logs, and a few thoughts:
"workingenv.py -r http://some/place.txt"; is a way you can build something like a distribution, that's separate from any of the pieces that make it up. That way you can build a full stack with all the components, without putting in any requirements in the individual pieces.
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.
* You can use a single templating system across all your applications (or at least a small number of systems), and use a search path and filename conventions to have them share style. This is probably more comfortable to people, but of course requires a single templating system. This also requires some improvements in the Buffet API (which are long overdue anyway).
-- 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 -~----------~----~----~----~------~----~------~--~---
