Falcon tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP resource crash my app? Why are trailing slashes trimmed from req.path? Why are field names in URI templates restricted to certain characters? Why is my query parameter missing from the req object? How can large-scale 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

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic large-scale 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 HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds

Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic Requests coming in for either path will be sent to the same resource. Why are field names in URI templates restricted to certain characters? Field names are restricted to the ASCII characters in the set HTTP response to that request. By convention, these are called req and resp, respectively. Route templates and hooks can inject extra params, as we shall see later on. Right now, the image resource responds