CherryPy Project Download

The dispatcher is in charge of mapping the requested path to an object, and setting cherrypy.response.body or raising a 404. If you don't like the way CherryPy does this by default you can easily change it. You can even use multiple dispatchers to control different parts of your application. Basically, a dispatcher can be any callable that accepts a path as an argument.

For example, here's a simple dispatcher that uses Routes:

import cherrypy 
import routes 
class MethodDispatch: 
    A Routes based dispatcher for CherryPy
    Based on
    def __init__(self): 
        self.mapper = routes.Mapper() 
        self.controllers = {} 
    def redirect(self, url): 
        raise cherrypy.HTTPRedirect(url) 
    def connect(self, name, route, controller, conf={}, **kwargs): 
        self.controllers[name] = controller 
        self.mapper.connect(name, route, controller=name, **kwargs) 
    def finalize(self): 
    def dispatch(self, path): 
        """ Find the right page handler """ 
        request = cherrypy.request 
        # Tell routes to use the cherrypy threadlocal object 
        config = routes.request_config() 
        if hasattr(config,'using_request_local'): 
            config.request_local = lambda: request 
            config = routes.request_config() 
        # Hook up the routes variables for this request 
        config.mapper = self.mapper = request.headers.get('host',None) 
        config.protocol = request.scheme 
        config.redirect = self.redirect 
        config.mapper_dict = self.mapper.match(path) 
        if config.mapper_dict: 
            c = config.mapper_dict.get('controller',None) 
            if c: 
                controller = self.controllers[c] 
                methods = ('OPTIONS','GET','HEAD','POST', 
                if request.method not in methods: 
                    raise cherrypy.HTTPError(400,'Bad Request') 
                # If request method is HEAD, return the page handler 
                # for GET, and let CherryPy take care of dropping  
                # the response body 
                method = request.method 
                if request.method == "HEAD": 
                    method = "GET" 
                page_handler = getattr(controller,method,None) 
                if not page_handler: 
                    raise cherrypy.HTTPError(501,'Not Implemented') 
                cherrypy.response.body = page_handler(**request.params) 
        # No page handler found 
        raise cherrypy.NotFound(path) 

No black magic or anything scary involved. Although the dispatcher wouldn't have to be a class it's more useful this way as it can be more easily used as a component. The dispatcher code above gives you a clear distinction between different HTTP methods. Now you can write code like this:

class Test: 
    def GET(self, **kwargs): 
        return '''''<form method="post" action="/">
        <input type="text" name="test" value="test">
        <input type="submit"></form>''' 
    def POST(self, **kwargs): 
        return kwargs['test']

dispatcher = MethodDispatch()
# Add a route to our controller
dispatcher.connect(name='Test', route='/', controller=Test(), conf=config)

# Update the config to use our new dispatcher
config = {'environment': 'production',
          'request.dispatch': dispatcher.dispatch,


That's how easy writing your own dispatcher is.

skam said on 2006-06-24 16:16

Good! It looks like

Sylvain said on 2006-05-04 03:50

Nice article :)

guest said on Fri Aug 28 02:13:21 2015

Can you provide examples of how to hook this up via a config file?

Hosted by WebFaction

Log in as guest/cherrypy to create/edit wiki pages