On Fri, Oct 22, 2004 at 10:16:17AM -0400, Michael wrote: > I can have my plugin set the CGIAPP_PLUGIN_APACHE environment variable. > Then any other plugins can see that and act accordingly. For instance, > you could check for this env var before setting a cookie to either use > CGI.pm's cookie() or use Apache::Cookie(). Then you could either use > header_add() or query->header_out() to add it. Thoughts?
Hmm, I don't like the idea of setting environment values--seems like it could get messy. Why can't C::A::P::Cookie check the type of object that it gets from $self->query and behave accordingly? > This might actually be a way for all plugins to communicate with each > other. We had a previous discussion about whether some plugins might > want to be able to detect if others where there. For instance, an auth > and session plugin. Other thoughts? I don't have any other bright ideas so setting an environment variable may be sufficient. However, in cases like this one, it seems far more effective to use data on hand instead of adding complexity to our applications. 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]
