expressjs/routification

DEPRECATED

Routification

Turn any connect app into an Express-like router. In the future, Express will be a Routification instance. Unlike Express 3.0, each route is its own middleware. You will probably see a very insigificant performance drop, but there's no more implicit app.use(app.router) you have to worry about.

Routification is built on path-to-regexp. If you have any issues with path matching, please open an issue in that repository instead.

Routification assumes you've npm install connect yourself. It does not rely on connect itself.

API

var app = routification([app], [options])

app is an optional connect instance. options are passed to path-to-regexp.

var routify = require('routification')
var app = routify()
var app = routify(connect())
var app = routify({
  sensitive: true
})
var app = routify(connect(), {
  sensitive: true
})

app[VERB](path || regexp, middleware...)

Verb can be any HTTP method supported by node. delete is also aliased as del. Each middleware should have a signature of (req, res) or (req, res, next).

Note: if the request method is HEAD, it will also match any GET routes as well. To match HEAD and not GET, do app.head() before any app.get().

app.all(path || regexp, middleware...)

Will match any request with the given path or regexp.

License

The MIT License (MIT)

Copyright (c) 2013 Jonathan Ong [email protected]

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.

routification's Issues

app.route(path || regexp)[VERB](middleware...)

migrated from expressjs/express#1501

routification[method](path, fn, options)

should create middleware, but don't automatically app.use() since there's no underlying connect instance. similar to https://github.com/koajs/route

archive this repo?

ref: expressjs/discussions#134

@jonathanong @vendethiel - you have been identified as the last / most active committer in this repo which is inactive for a while. This ping is to check with you to determine:

• whether do you have any specific maintenance plans with this repo
• are you fine for this repo to be archived
• do you believe if there is another stake holder / affected party who should know

thanks!

allow each route to have multiple callbacks

will require each route to have a dispatcher, which is complicated. also, only do this if its faster, so benchmarks are required.

maybe use ware