that take a user-suppiled lambda to generate the data needed to render our desired compile-time resource! These are e�ectively templated functions, but we will use the cleaner auto parameter syntax for

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response API Class Req/Resp Cookies Status Codes Error Handling Redirection Middleware Components Hooks Routing Utilities Testing Changelogs 1.0.0 0.3.0 0.2.0 Created using Sphinx 1.3.5. index modules | next authorize the request, taking into account the user’s role and the requested resource. Why doesn’t Falcon create a new Resource instance for every request? Falcon generally tries to minimize the number

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response Class Request & Response Cookies Status Codes Error Handling Media Redirection Middleware Hooks Routing Utilities Testing Community Guide Get Help Contribute to Falcon FAQ Changelogs 1.4.1 1.4.0 1 tests Serving Images Introducing Hooks Error Handling What Now? FAQ Design Philosophy Performance Routing Extensibility Request Handling Response Handling Misc. Introduction Perfection is finally attained

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request deployments. Features • Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response process_response(self, req, resp, resource): if 'result' not in resp.context: return resp.body = json.dumps(resp.context['result']) def max_body(limit): def hook(req, resp, resource, params): length = req.content_length

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • No reliance on magic globals for routing and state management • Easy access to headers and

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response Class Request & Response Cookies Status Codes Error Handling Media Redirection Middleware Hooks Routing Utilities Testing Community Guide Get Help Contribute to Falcon FAQ Changelogs 1.4.0 1.3.0 1 tests Serving Images Introducing Hooks Error Handling What Now? FAQ Design Philosophy Performance Routing Extensibility Request Handling Response Handling Misc. Introduction Perfection is finally attained

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response Class Request & Response Cookies Status Codes Error Handling Media Redirection Middleware Hooks Routing Utilities Testing Community Guide Get Help Contribute to Falcon FAQ Changelogs 1.4.1 1.4.0 1 tests Serving Images Introducing Hooks Error Handling What Now? FAQ Design Philosophy Performance Routing Extensibility Request Handling Response Handling Misc. Introduction Perfection is finally attained