> wrowe 01/11/19 19:49:50
>
> Modified: . STATUS
> Log:
> Split Justin's and my key issues, which have become tangled (yet have
> nothing to do with one another.)
>
> Revision Changes Path
> 1.341 +8 -2 httpd-2.0/STATUS
>
> Index: STATUS
> ===================================================================
> RCS file: /home/cvs/httpd-2.0/STATUS,v
> retrieving revision 1.340
> retrieving revision 1.341
> diff -u -r1.340 -r1.341
> --- STATUS 2001/11/20 03:14:05 1.340
> +++ STATUS 2001/11/20 03:49:50 1.341
> @@ -1,5 +1,5 @@
> APACHE 2.0 STATUS: -*-text-*-
> -Last modified at [$Date: 2001/11/20 03:14:05 $]
> +Last modified at [$Date: 2001/11/20 03:49:50 $]
>
> Release:
>
> @@ -79,7 +79,13 @@
> to make it agree with the operation of the StartServers
> directive.
>
> + * revamp the input filter syntax to provide for ordering of
> + filters created with the Set{Input|Output}Filter and the
> + Add{Input|Output}Filter directives. At minimum, some sort
> + of insert first v.s. append to end or 'relative to x' is
> + probably needed.
What if... we were to make the syntax be filtername[{+|-}{0..10}]? Such
that -10 (CONTENT-10 == 0) was closest to the handler, and +10
(CONTENT+10, HTTP) was closest to the network? Charset transliteration
to a common denominator (e.g. utf-8) might happen at +9, while SSI
scripts might operate at -9.
Just a thought. Dunno if it makes any sense, but it would offer some
level of control.
Bill
