view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    DispatchISA introduced some convenience, but some headaches as well - if
    you inherit from a class that uses AutoLoader then ALL method calls are
    true. And as just explained, AUTOLOAD() will not know what the called
    method was. This may represent a problem if you aren't aware that, say,
    CGI.pm uses AutoLoader and spend a few hours trying to figure out why
    all of a sudden every URL under Dispatch is bombing. You may want to
    check out NEXT.pm (available from CPAN) for use in your AUTOLOAD
    routines to help circumvent this partucular feature.

    If you decide to use DispatchISA it is HIGHLY SUGGESTED that you do so
    with DispatchAUTOLOAD Off (which is the default behavior).

NOTES
    If you define a dispatch_index() method calls to /Foo will default to
    it. Unfortunately, this implicit translation only happens at the highest
    level - calls to /Foo/Bar will translate to Foo->Bar() (that is, unless
    Foo::Bar is your DispatchPrefix, in which case it will work but
    /Foo/Bar/Baz will not, etc). Explicit calls to /Foo/index follow the
    normal dispatch rules.

lib/Apache/Dispatch.pm  view on Meta::CPAN

DispatchISA introduced some convenience, but some headaches as well - 
if you inherit from a class that uses AutoLoader then ALL method calls
are true.  And as just explained, AUTOLOAD() will not know what the
called method was.  This may represent a problem if you aren't aware
that, say, CGI.pm uses AutoLoader and spend a few hours trying to 
figure out why all of a sudden every URL under Dispatch is bombing.
You may want to check out NEXT.pm (available from CPAN) for use in 
your AUTOLOAD routines to help circumvent this partucular feature.

If you decide to use DispatchISA it is HIGHLY SUGGESTED that you do so
with DispatchAUTOLOAD Off (which is the default behavior).

=head1 NOTES

If you define a dispatch_index() method calls to /Foo will default to
it.  Unfortunately, this implicit translation only happens at the
highest level - calls to /Foo/Bar will translate to Foo->Bar() (that
is, unless Foo::Bar is your DispatchPrefix, in which case it will
work but /Foo/Bar/Baz will not, etc).  Explicit calls to /Foo/index
follow the normal dispatch rules.

lib/Apache2/Dispatch.pm  view on Meta::CPAN

DispatchISA introduced some convenience, but some headaches as well - 
if you inherit from a class that uses AutoLoader then ALL method calls
are true.  And as just explained, AUTOLOAD() will not know what the
called method was.  This may represent a problem if you aren't aware
that, say, CGI.pm uses AutoLoader and spend a few hours trying to 
figure out why all of a sudden every URL under Dispatch is bombing.
You may want to check out NEXT.pm (available from CPAN) for use in 
your AUTOLOAD routines to help circumvent this partucular feature.

If you decide to use DispatchISA it is HIGHLY SUGGESTED that you do so
with DispatchAUTOLOAD Off (which is the default behavior).

=head1 NOTES

If you define a dispatch_index() method calls to /Foo will default to
it.  Unfortunately, this implicit translation only happens at the
highest level - calls to /Foo/Bar will translate to Foo->Bar() (that
is, unless Foo::Bar is your DispatchPrefix, in which case it will
work but /Foo/Bar/Baz will not, etc).  Explicit calls to /Foo/index
follow the normal dispatch rules.