> You can subclass Apache::RegistryNG to do what you want and send the
> patch for others to re-use.
The perldoc Apache::Registry says
"Apache::Registry - Run unaltered CGI scrips under mod_perl"
Thus I guess if I have to amend Apache::Registry it might be worth
submitting a pach for a bugfix rather than a subclass of this module
wouldn't it?
> The idea is interesting but while the implementation is possible it
> won't give any speed benefit. The positive effect that can be achieved
> is returning the caller exactly what it has asked for.
I don't understand you here. It might not give any speed benefits in
computing the headers, sure. But there are number of things that you
might want to be in the headers (like date last modified, md5 checksum,
content language, content length, etc) and they need the whole page to
be computed anyway.
You could argue that sending minimalistic headers to speed up head
requests is possible, but then you're fucking proxies which are there to
save you bandwidth and CPU anyway.
> When I think more about it may be if PerlSendHeader is On, we can adjust
> the code that parses the script's output in search for headers, to
> return when it finds the 'Content-type' header.
Maybe there should be an option, like
ManageHeadRequests [On|Off]
The option might be 'Off' by default for backwards compatibility.
That would do the Right Thing whenever a HEAD request is invoked on the
script. I'm quite surprised that this whole issue doesn't seem to have
been raised yet - or maybe I missed something?
What do you guys think?
Cheers,
--
== \______ =====================================================
/\____/\ IT'S TIME FOR A DIFFERENT KIND OF WEB
/ /\__/\ \
_/_/_/\/\_\_ Jean-Michel Hiver - Software Director
\ \ \/*/ / [EMAIL PROTECTED] +44 (0)114 221 4968
\ \/__\/
\/____\ VISIT HTTP://WWW.MKDOC.COM
== / ===========================================================
