Adds support for mapping and inferring formats to content types.
Adds support for mapping and inferring formats to content types.
$ - Provides a request-scoped format variable $ - Maps formats to content types and vice versa $ - Augments the content-type inferrer to use the format
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet. These traits should not be mixed in SkinnyMicroBase.
Async skinny.micro filter.
Async skinny.micro servlet.
Content encoding
Content encoding
Represents an HTTP content encoding.
Represents the value of a content negotiation header.
Response body format.
A Handler
is the SkinnyMicro abstraction for an object that operates on a request/response pair.
Trait representing an object that can't be fully initialized by its constructor.
Trait representing an object that can't be fully initialized by its constructor. Useful for unifying the initialization process of an HttpServlet and a Filter.
A utility to help with mime type detection for a given file path or url
Represents concurrency issue access multiple threads on the Servlet.
The base implementation of the SkinnyMicro DSL.
The base implementation of the SkinnyMicro DSL. Intended to be portable to all supported backends.
Represents an exception happened inside skinny.micro.
An implementation of the SkinnyMicro DSL in a filter.
An implementation of the SkinnyMicro DSL in a filter. You may prefer a filter to a SkinnyMicroServlet if:
$ - you are sharing a URL space with another servlet or filter and want to delegate unmatched requests. This is very useful when migrating legacy applications one page or resource at a time.
Unlike a SkinnyMicroServlet, does not send 404 or 405 errors on non-matching routes. Instead, it delegates to the filter chain.
If in doubt, extend SkinnyMicroServlet instead.
SkinnyMicroServlet
Base trait for SkinnyMicroFilter implementations.
Params.
An implementation of the SkinnyMicro DSL in a servlet.
An implementation of the SkinnyMicro DSL in a servlet. This is the recommended base trait for most SkinnyMicro applications. Use a servlet if:
$ - your SkinnyMicro routes run in a subcontext of your web application. $ - you want SkinnyMicro to have complete control of unmatched requests. $ - you think you want a filter just for serving static content with the default servlet; SkinnyMicroServlet can do this too $ - you don't know the difference
SkinnyMicroFilter
Base trait for SkinnyMicroServlet implementations.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet. These traits should not be mixed in SkinnyMicroBase.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet. These traits should not be mixed in SkinnyMicroBase.
Async skinny.micro filter.
Async skinny.micro servlet.
An implementation of the SkinnyMicro DSL in a filter.
An implementation of the SkinnyMicro DSL in a filter. You may prefer a filter to a SkinnyMicroServlet if:
$ - you are sharing a URL space with another servlet or filter and want to delegate unmatched requests. This is very useful when migrating legacy applications one page or resource at a time.
Unlike a SkinnyMicroServlet, does not send 404 or 405 errors on non-matching routes. Instead, it delegates to the filter chain.
If in doubt, extend SkinnyMicroServlet instead.
SkinnyMicroServlet
An implementation of the SkinnyMicro DSL in a servlet.
An implementation of the SkinnyMicro DSL in a servlet. This is the recommended base trait for most SkinnyMicro applications. Use a servlet if:
$ - your SkinnyMicro routes run in a subcontext of your web application. $ - you want SkinnyMicro to have complete control of unmatched requests. $ - you think you want a filter just for serving static content with the default servlet; SkinnyMicroServlet can do this too $ - you don't know the difference
SkinnyMicroFilter
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet.
Built-in features in SkinnyMicroFilter/SkinnyMicroServlet. These traits should not be mixed in SkinnyMicroBase.
Represents unstable access to servlet objects managed by containers from unmanaged threads.
Unstable access validation configuration.
Adds support for generating URIs from routes and their params.
Defines type classes and helper methods for well known content-negotiation headers.
Response body formats.
Immediately halts processing of a request.
Immediately halts processing of a request. Can be called from either a before filter or a route.
the status to set on the response, or null to leave the status unchanged.
a result to render through the render pipeline as the body
headers to add to the response
the HTTP status reason to set, or null to leave unchanged.
Immediately exits from the current route.
Immediately exits from the current route.