Kevin Dangoor wrote:
Jeff has designed an identity API that is amazingly user friendly for common cases. I would like to brainstorm a bit on how this API might be tweaked to use RuleDispatch syntax which would provide more flexibility going forward. That brainstorming should be in a separate thread. I'd like to do that brainstorming before 0.9, because I'd rather not have such a large backwards-incompatible change afterwards.
If you are thinking about RuleDispatch, you should probably consider peak.security: http://peak.telecommunity.com/DevCenter/SecurityRules
Which brings me to PasteDeploy. Ian has been keeping up with the CherryPy 2.2 changes and trying to make sure that the level of WSGI support needed for PasteDeploy is met by CP 2.2's more flexible routing. The CP2.2 transition is something we can make for TG0.9, but the PasteDeploy transition is not. I do think that using PasteDeploy is a good goal and that it should be done right when CP is ready for it.
Right now CherryPy is the blocker, and once it is working there I think that should transfer to TG fairly easily, possibly (hopefully) even retroactively (e.g., if you are running TG 0.9 with whatever version of CherryPy where this is working). Right now CherryPy isn't offering a sufficient WSGI-related API, and I don't know if that's because of underlying architectural issues, or that the APIs just don't expose what they should.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
