> -----Original Message----- > From: Graham Leggett > Sent: Donnerstag, 4. November 2010 17:33 > To: [email protected] > Subject: NULL handler, NULL input and output filters > > Hi all, > > On a number of occasions I've had to "cap" the input or > output filter > stacks with a NULL filter that either discards buckets, or > returns an > empty brigade in response to a read. I have always had to be careful > to name these duplicated filters carefully so they don't clash with > one another, even though they all do the same thing. > > I now face the need for a NULL handler - a simple handler > that returns > an empty document, and that's it, because the real work was > being done > by another module adding a header to the response. Sure, I > can create > an empty file to fudge this, but in this particular case the URL is > likely to be hit often, and performance matters for us. > > These things look like things the server should do out the > box, and be > available to any module that may want them. They are also simple, > small, and entirely configuration free. > > Would such filters and the handler fit into the core, or > would they go > into something like mod_request, or mod_null? Ideally, I'd like the > filters to go into the core, and have the handler go into mod_null. > Thoughts?
I would like to see them all (filters and handler) in a new mod (e.g. mod_null). Regards Rüdiger
