Define the filter API

[ghost]

Originally reported by: Anonymous

---

We need to define the full api for the filters. [[br]]
There are two seperate baseobjects, but there is still '''one''' list.

We wanted to change it if i'm not mistaken into two lists.

• One for incoming, (BaseInputFilters)
• and one for outgoing. (BaseOutputFilters)

This would allow for more advanced (but in no case rare) setups.

Futhermore we need to have our api ready to convert all the filters (the longer we wait, the more difficult it will get to change the filters), and to move several other items to filters as well:

• Sessions (it's an option, i know :) )
• CSAuthenticate (as this interferes with any generator based templating filter)
• Caching ?

Moving more features to filters allows the end programmer to have more control, and to decrease the need to patch the server directly. This will make it easier for developers to migrate to CherryPy.

Reported by remco.boerma@gmail.com

---

• Bitbucket: https://bitbucket.org/cherrypy/cherrypy/issue/50

[ghost]

Original comment by Remco Wendt (Bitbucket: remco, GitHub: remco):

---

See #38 as well

[ghost]

Original comment by Anonymous:

---

This is done now.
We still keep only one queue, but we split filters into input filters and output filters.

[ghost]

Original comment by Remco Wendt (Bitbucket: remco, GitHub: remco):

---

So we've split the filters. But in fact, nothing changes. also not the order in which the output filters are called vs the order in which the inputfilters are called.

I will try to make things more clear, and put them in the experimental using a different implementation