-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Malthe Borch wrote:
> Currently the predicates pertain only to views, regardless of whether > they're declared using a <route> or a <view> directive (or using the > ``bfg_view`` decorator). > > I would expect that if you declare a predicate on the route, that the > route would only be used if that predicate matches. Instead, the route > is used regardless, while the view which is declared on that same > route is guarded with the predicate check. > > Does it make sense (and is it feasible in terms of > backwards-compatibility concerns) to have the predicate be matched > against the route, and if it does not match, go on to the next route? I'm not sure I understand: routes already behave as predicates, and chain exactly as you describe. The view predicates are there to allow selecting a particular view among several registered for the route or context: e.g., to dispatch to different views for GET versus POST for the same route / context and view name. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrgiboACgkQ+gerLs4ltQ5rFwCfcXDoxPGb1GimRe9mgy9D5qEx tNMAn2wBU+460wN7Hrgm5S8sdlU5vqX3 =L9F+ -----END PGP SIGNATURE----- _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
