> I actually think that since Registry exists to be backwards compatible > with mod_cgi, it should emulate mod_cgi as closely as it can, including > the nph support.
I go back and forth on this issue. while Registry comes close to emulating mod_cgi, the point I waver on is whether we really should bill it as a drop-in replacement - in the history of Registry, I honestly doubt if there has been a single user that really was able to 'drop-in' a mod_cgi script and have it work without alteration. well, ok, maybe that's an exaggeration :) > Does mod_cgi still look for /nph-/ in script names? stas said so in a previous message, IIRC. I haven't looked. > If > so, Registry should do it too. that's where I'm not sure. what's the real goal with registry - to provide 100% compat with mod_cgi or to make mod_cgi-like scripts run as fast as they can? the reason I suggested a subclass was so that the rare people who require nph scripts have an outlet, while the vast majority of users are not burdened with the overhead of checking for nph- scripts on every request. at least that's my thought today. as I said, I tend to change my view every few months :) > > Am I correct in thinking that this is not an issue at all if you are not > using Registry, i.e. mod_perl will not send out any automatic headers if > you don't ask it to? mod_perl doesn't send headers anymore - the header filter in apache 2 core does that now. there is no $r->send_http_header() method. > > I'd really prefer to have a better name for assbackwards if it's going > to be used as a public API. Maybe we could make an alias for it that > explains its purpose more clearly. this one I do feel strongly about. however insane it is to have a public assbackwards() API, mod_perl should just be offering up the Apache API as it is and getting out of the way. that's what it's called in the Apache API, so $r->assbackwards needs to stay. if you feel strongly about an alias, I guess we can do that, but I wouldn't want a user to try accessing a part of the request_rec by name and have it not be there. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
