-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Tim Bray wrote: > The saving grace is that the httpd & modules code is generally very > transparent and readable. In every case, when I was puzzled as to (a) > what does apr_furgle_brolly() really do? or (b) how do I accomplish > XXX? I was able to track the answer down by poking around *.[ch].
Yes, that's true. But taken form another point of view, a more "architectural" point of view let's say, I can't believe I had to go through mod_perl's EXCELLENT documentation (1) to understand WHY apache is not allowing extra headers when I write a fully-rewriting input connection filter for mod_openpgp. (3) Of course, we have amazing books, like Nick Kew's, but still! References: 1 - http://perl.apache.org/docs/2.0/user/handlers/filters.html 2 - http://perl.apache.org/docs/2.0/user/handlers/filters.html#Connection_Input_Filters 3 - http://linux-consulting.buanzo.com.ar/2007/07/apache-frustration-p.html - -- Arturo "Buanzo" Busleiman - Consultor Independiente en Seguridad Informatica SHOW DE FUTURABANDA - Sabado 18 de Agosto 2007 (Speed King, Capital Federal) Entradas anticipadas a traves de www.futurabanda.com.ar - Punk Rock Melodico -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGpjOpAlpOsGhXcE0RCpk6AJ97XPHAS6AaCKDmYQxKi54Mfd5jcgCcCGFj B9hi8b/7Cp/cU5nHNuaK+/g= =Ju0e -----END PGP SIGNATURE-----
