On Sat, Mar 29, 2008 at 6:41 AM, André Warnier <[EMAIL PROTECTED]> wrote:
> Just for the rest of us : does anyone care to summarise what works and
> works not (inasfar as not necessarily documented and/or intuitive) ?
I think it's pretty well-documented:
http://perl.apache.org/docs/2.0/user/port
On Wed, Mar 26, 2008 at 9:47 AM, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> > what about...
> >
> > PerlAccessHandler JetSet::Handler::AccessHandler
> >
> > sub AccessHandler {
> > my ($r) = @_;
> > }
>
> We seem to have solved the problem, but for the sake of conversation...
>
> Whe
On Wed, Mar 19, 2008 at 2:41 PM, John ORourke <[EMAIL PROTECTED]> wrote:
> The only down-side is that (AFAICR) it is creating a new object for each
> request
No, it's a class method. No object is created.
> PerlResponseHandler $My::Handlers::Persistent->response_handler
> PerlFixupHandler $M
On Wed, Mar 19, 2008 at 2:22 PM, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> In order to have many handlers in a file, I've put the following lines
> and other, similar lines in my virtual host configuration:
>
> PerlAccessHandler JetSet::Handler->AccessHandler
> PerlResponseHandler JetSet::Ha
I imagine you're already aware of this, but just in case...
"PerlInitHandler
When configured inside any container directive, except ,
this handler is an alias for PerlHeaderParserHandler described earlier.
Otherwise it acts as an alias for PerlPostReadRequestHandler described
earlier."
(htt
� wrote:
Just for the rest of us : does anyone care to summarise what works
and works not (inasfar as not necessarily documented and/or
intuitive) ? And maybe what the original point of this interesting
thread was ?
Sure, but I don't think we're finished quite yet. ;)
Colin
Jonathan Vanasco wrote:
On Mar 28, 2008, at 3:11 PM, Colin Wetherbee wrote:
Care to add one, just to see what happens? :)
You know you've been working too much on the Business Side when you stop
testing stuff like that automatically. sigh...
Indeed. :)
ok...
it works if i have
[snip]
