Malthe was also looking for some way to insert HEAD data (script tags/ css) into a rendering based (loosely) on a template name. This might be a reasonable solution for specifying *which* elements to include as long as the decision can be made using the URI alone.
- C On Aug 29, 2008, at 12:33 AM, Tres Seaver wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The W3 hava a spec, proposed by Akamai, for a remarkably Zope-ish > feeling approach: > > http://www.w3.org/TR/urispace.html > > It came up on the Squid developers' list in the context of making > "smarter" ACLs, but seems like it could be a useful generic middleware > component / library, e.g. to support declarative security, fine- > grained > cache control, etc. > > I've started a cut at it: > > http://svn.repoze.org/repoze.urispace/trunk > > and in particular: > > http://svn.repoze.org/repoze.urispace/trunk/README.txt > > and wonder if others would find it useful. > > I am also corresponding with the original author of the spec, Mark > Nottingham, to clarify one ambiguity in the spec (I think it reads > that > '<path match="foo"> only fires if 'foo' is the "next" element in the > path; I would like a way to spell both "any" element and "last" > element). > > > Tres. > - -- > =================================================================== > Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] > Palladion Software "Excellence by Design" http://palladion.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIt3wI+gerLs4ltQ4RAtZbAJ9CJ5TQnGIrovA2ludjvPTf6NDBRgCfUZQS > Bl0VhMpy/aL+yZcsPmpkE/E= > =9aPB > -----END PGP SIGNATURE----- > _______________________________________________ > Repoze-dev mailing list > Repoze-dev@lists.repoze.org > http://lists.repoze.org/listinfo/repoze-dev > _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
