Trie-based URL and Method Routing for Node.js
Dispatchington is a trie-based URL and method router for Node.js based on routington. It can almost be used as a drop-in replacement. For information on its motivations, read about The Imperfections of Express.
When should you use this?
405 Method Not Allowedautomatically
501 Not Implementedautomatically, assuming you use the middleware
var dispatchington = require'dispatchington'var router = dispatchington
To mount the middleware:
var app = expressappuserouterimplementedMethods// static stuff// cookie stuff// session stuffappuserouterdispatcher// 404 handler// error handler
You can still use the router without Express or Connect:
var dispatcher = routerdispatcher// Map of methods implemented by the server.// All methods are lowercased.var methods = routermethods// ...// Define routes// ...httpcreateServeron'request'if !methodsreqmethodtoLowerCaseresstatusCode = 501resend'Not Implemented'returndispatcherif errresstatusCode = errstatus || 500resenderrmessage || 'Internal Server Error'return// If this point is reached,// no route has been matchedresstatusCode = 404resend'Not Found'listenprocessenvPORT || 80
You can define stacks of middleware, either a single function or an array of functions, with a name. These stacks can then be referenced by name.
After defining the following stacks:
The following simplified stack:
routerget'/' 'compress' 'session'
is equivalent to all of the following:
routerget'/' connectcompress connectcookieParser connectcookieSessionrouterget'/' connectcompressconnectcookieParserconnectcookieSessionrouterget'/'connectcompressconnectcookieParserconnectcookieSession
The idea is that you turn your middleware stacks into legos.
You can define them early in your app,
then re-use them throughout your routes without
require()ing each of them from an external "common" module.
It will also make your routes much more readable as,
ideally, it could look something like this:
routerget'/''compress''cache if visitor''accept html only''retrieve session''retrieve user''check if allowed''parse body'handlerresrender'homepage'
You will know exactly what happens before you execute the handler. You can use or don't use specific middleware very easily depending on the URL or method matched.
For information on how the routing strings actually work, view routington's documentation.
There are two ways to create a route. The first is Express' method-first way:
routerget'/things' 'compress' 'session' handlerrouterpost'/things' 'compress' 'session' handlerrouterput'/things' 'compress' 'session' handler
The other is by defining a route, then adding stacks based on the method:
routerroute'/things'get'compress' 'session' handlerpost'compress' 'session' handlerput'compress' 'session' handler
In both versions, you can define multiple routes at the same time:
routerroute'/things''/thing/:id'get'compress' 'session' handlerpost'compress' 'session' handlerput'compress' 'session' handlerrouterget'/things''/thing/:id''session' handler
If you define a route like so:
You can retrieve the value of
id just like in Express:
reqid = reqparamsidnext
The trie, specifically the routington instance,
is accessible at
You can manipulate it however you'd like.
View its documentation for more information.
app.allis not supported. Simply define a stack and use it in every method.
npm install methodsfor a list of all possible methods.
The MIT License (MIT)
Copyright (c) 2013 Jonathan Ong email@example.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.