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 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 second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to serve all requests coming

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 the requested resource. Tip The Talons project [https://github.com/talons/talons] maintains a collection of auth plugins for the Falcon framework. Why doesn’t Falcon create a new Resource instance for second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to server all requests coming

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 • Easy access to headers and bodies through request and response classes • DRY request process_response(self, req, resp, resource): if not hasattr(resp.context, 'result'): return resp.body = json.dumps(resp.context.result) def max_body(limit): def hook(req, resp, resource, params): length = req

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 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 second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to serve all requests coming

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 • Easy access to headers and bodies through request and response classes • DRY request 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

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 • Easy access to headers and bodies through request and response classes • DRY request 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

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 • Easy access to headers and bodies through request and response classes • DRY request 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

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 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 second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to serve all requests coming

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 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 second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to serve all requests coming

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 requests? Why doesn’t Falcon create a new Resource instance for every request? Is Falcon thread-safe? How do I implement both POSTing and GETing items for the same resource? How can I pass data from a hook to cookie, but it isn’t being passed back in subsequent requests. Why does raising an error inside a resource crash my app? Why are trailing slashes trimmed from req.path? Why are field names in URI templates