You can find more information on the speaker's site:
- Abstract: http://sartak.org/talks/yapc-asia-2010/path-dispatcher/
- Talk: http://sartak.org/talks/yapc-asia-2010/path-dispatcher/
Path::Dispatcher solves the problem of "dispatch" - mapping a string (the path) through a set of rules to find matches and then act upon them. Most commonly this is done in web applications to run one or more actions based on each incoming request URI. However, Path::Dispatcher, unlike most of the other modules in its niche, is not married to the web. It is also used to dispatch based on command-line arguments in Prophet/SD, and to dispatch commands in a MUD engine.
This talk (since being presented at YAPC-NA) has become a case study in Moosey design, describing how the needs of Path::Dispatcher's users have influenced its evolution. Too many talks present a topic as though the solution sprung fully-formed from the designer's brain in an instant, ignoring the interesting details of how a system is improved over time. I'm here to talk about this overlooked subject!