On Jan 30, 2006, at 2:25 PM, Ian Bicking wrote:
Kevin Dangoor wrote:
Here's my philosophy on stuff like this: I aim for TurboGears to be
best-of-breed. The definition of "best-of-breed" will change over
time. (It'll also vary from person to person, but there's not much I
can do about that.) As "the best" changes, I'd like to see TurboGears
change with it. Of course, changes need to have reasonable migration
paths and all of that, which is the primary limiting factor. But, the
bigger the win, the easier it is to justify a slightly more painful
transition.
...
* Filters. CP-style filters could be implemented in RhubarbTart,
but I'd rather just not. The filters in TG could be reworked or
have extra interfaces to be phrased as WSGI middleware. I think
the actual application-facing interface to things like Identity
don't need to be changed, so this might not be an issue. Since TG
uses decorators more than filters (for app-visible APIs), I think
this is mostly OK as-is.
In my experience, filters are a bad API anyway. Every time I've ever
wanted to use a filter, it was for a particular URL, which isn't
really supported without lots of jiggering.
-bob
