Comments on --verbose: Request Routing With URI Templates in Node.JS

I'd check if the request.method exists in the ...

2010-02-21T07:24:18.057-08:00

I'd check if the request.method exists in the handler and return a 405 otherwise.

Clearer syntax is the point. How often do you nee...

2009-12-29T07:04:41.901-08:00

Clearer syntax is the point. How often do you need the full power of RegExp for path parsing? Rarely. And you end up with typos, unintentionally greedy patterns that match other handlers' request paths. Really RegExp is overkill.

PLUS- this method uses the variable {names} from the URI template as the actual variable names returned in a match. So you don't have to iterate through the RegExp match groups manually looking for a parameter from the URI.

Hmm. But it's still ends up as a regex. What&#...

2009-12-24T02:58:11.806-08:00

Hmm. But it's still ends up as a regex. What's the point (besides somehow clearer syntax)? Regex-only URI (like the ones implemented in `nerve`) will be much more flexible.

On the other hand, for simple tasks as this, I think clear syntax will outweight other concerns.

Hm. It just occurred to me that the URI template p...

2009-11-22T11:41:30.951-08:00

Hm. It just occurred to me that the URI template parameter-to-function-parameter mapping is positional, so that the names in the template must be in the same order as the names in the handler function. So you could't change /comments/ handler to take (commentId, postId) and have it still work. This code would produce the reverse of what would would expect for those two parameter values.

Instead of calling apply() with the parameter array, it could just pass in the Route.parse() results as a single parameter to the handler.