Why do we pass request and connection to ap_add_*_filter? If we pass a
request, the connection is redundant, and currently passing NULL for the
request means use the connection - however we always pass the
connection, and, indeed, I think code relies on that. This strikes me as
unclean and mildly confusing. I'd rather have ap_add_request_*_filter
and ap_add_connection_*_filter (even if they are just wrappers for what
we've got) - what do people think?

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff

ApacheCon 2001! http://ApacheCon.com/

Reply via email to