Skip to content

Define the filter API #50

Closed
Closed

Description

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


Activity

  1. ghost added on Apr 30, 2016
  2. ghost closed this as completedon Apr 30, 2016
  3. added a commit that references this issue on Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions