Handling Sessions with an 'Environment' #246

This can be used to add some compile time dependencies for Middleware and Plugins. To fix code broken by this, you will need to introduce a type parameter for Request, Response, MiddlewareResult and NickelError. ``` // e.g. This fn foo<'a>(&mut Request, Response<'a>) -> MiddlewareResult<'a> // Should become: fn foo<'a, D>(&mut Request<D>, Response<'a, D>) -> MiddlewareResult<'a, D> ``` You can add bounds to `D` in the above to place compile-time restrictions on the server data (can be used for configuration). BREAKING CHANGE

Also adds `on_send` which can be used to execute code when the Response headers are being sent.

The 1.2 beta has a regression for this kind of code, so being explicit should allow us to compile on all targets.

This is motivated to allow writing Plugins which are able to access both the current Response and Request without having to rely on odd syntax such as `(foo, bar).baz()`. BREAKING CHANGE: This breaks a *lot* of nickel usage, checking the diff from the examples should help to migrate code relying on the old structure.

This can sometimes be required when using some middleware which are predicated on the datatype of the Server. An alternative would be to litter the handler with extra type annotations (which is awkward without type ascription), or to use explicit type-annotated functions as middleware. Example usage: ``` middleware! { |res| <ServerData> // res is of type Response<ServerData> } ```

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Handling Sessions with an 'Environment' #246

Handling Sessions with an 'Environment' #246

Commits on Aug 1, 2015