Ferdinand Prantl

This is all about asynchronous tests, where the JavaScript code flow cannot be used to naturally place the `setUp` and `tearDown` sections. When a temporary resource needs to be created...

Would you consider adding this feature, please? It is essential if you develop an SPA and need to divide routing between the server and client routers; the last part of...

Will you consider this feature and/or the related PR #15, please? It is a KO criterion for anything but trivial server-side page handlers.

I released [`conenct-route-ext`](https://www.npmjs.com/package/connect-route-ext) including this feature.

Would you consider adding this feature, please? It is essential for non-trivial projects, where you need to support components and code sharing. Writing a chaining handler wrapper is a possible...

Will you consider this feature and/or the related PR #18, please? It significantly improves maintainability of the routing code.

I released [`conenct-route-ext`](https://www.npmjs.com/package/connect-route-ext) including this feature.

This may feel like a feature completing the interface, but I am not sure, if it has a real benefit in concrete applications. Handlers for different methods like `GET` and...

I've actually found one: adding members to `req` or `res` objects, if you want to reuse them in multiple requests. ```javascript router.all('/api/*rest', function (req, res, next) { res.sendData = function...

Another solution for performing shared code from my comment above would be allowing multiple handlers (#17). It would be probably better, because .the URL would not need to be parsed...