Chapter 3. Special Components: Dhandlers and Autohandlers
In previous chapters you’ve seen an overview of the basic structure and syntax of Mason components, and you’ve seen how components can cooperate by invoking one another and passing arguments.
In this chapter you’ll learn about dhandlers and autohandlers, two powerful mechanisms that help lend reusable structure to your site and help you design creative solutions to unique problems. Mason’s dhandlers provide a flexible way to create “virtual” URLs that don’t correspond directly to components on disk, and autohandlers let you easily control many structural aspects of your site with a powerful object-oriented metaphor.
Dhandlers
The term "dhandler”
stands for “default handler.” The
concept is simple: if Mason is asked to process a certain component
but that component does not exist in the component tree, Mason will
look for a component called dhandler
and serve that instead of the requested component. Mason looks for
dhandlers in the apparent requested directory and all parent
directories. For instance, if your web server receives a request for
/archives/2001/March/21 and passes that request
to Mason, but no such Mason component exists, Mason will sequentially
look for /archives/2001/March/dhandler,
/archives/2001/dhandler,
/archives/dhandler, and
/dhandler. If any of these components exist, the search will terminate and Mason will serve the first dhandler it finds, making the remainder of the requested component path available ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access