On Fri, Oct 22, 2004 at 11:44:44AM -0400, Michael wrote: > This would work if you could assume that since the query object is an > Apache::Request object that the user wants to send their HTTP headers > using query->header_out() as opposed to header_add(). But this isn't the > case. If they are using Apache::Request for their query object, but > aren't using my plugin for headers then trying to guess like that causes > problems if they decide to use header_add().
Michael, Just to be sure I'm following you, these issues would be a problem whether you were checking the ref type, using an ENV parameter or checking to see if a plugin is loaded as Rob suggested? I had only considered the cookie side of the equation which is relatively straight forward. As you've pointed out, the headers are going to be troublesome. It seems like you need to override all of the header_* methods in C::A if we're in a mp environment. Although I've been running my scripts under mp for a couple years now, I'm not very familiar with mod_perl development (thanks to Apache::Registry). Looking at the implementation of header_add, header_props and header_type (which are wrappers for CGI.pm header), I can see where it could be a potential headache to reimplement using A::Request. I wonder how MT is handling this situation; perhaps we can steal some code from them. William -- Knowmad Services Inc. http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
