Han Seoul-Oh

@lojjic @MinionMan: First of all, I'm sure you get this a lot because it's so well-deserved, but this library is an absolute treasure, thank you so much for writing it!...

@lojjic: It's definitely a better start than I had before! Thank you so much, will attempt and report back.

I did it! Sort of:  http://jsbin.com/rezosa/edit?js,output It was..._shockingly_ hard. The top Google results for "vml examples" didn't even work, they VML didn't render at all, it's just...

Node already has [an excellent query string parser](http://nodejs.org/api/querystring.html), but I see no reason why Choreographer would do that for you, since it's completely orthogonal to Choreographer's core routing functionality. I...

I won't comment on whether the arguments Choreographer passes in are "hacky", but there is precedent, Choreographer's routing API is based on Sinatra's. Your GET arguments code does make a...

Something that would help with such middleware and I think make sense as part of Choreographer would be a Sinatra-style `before` filter, e.g.: ``` js router.beforeGet('/register', function(callback, args, req, res)...

@lodewijkadlp I was definitely thinking the route in the `before` filter would be optional, defaulting to `/`, i.e. intercept all GET requests. As for orthogonality: when you say "Choreographer brings...

@gsf If you want to intercept all requests of a certain type, or to only do something for a particular route, then certainly a `before` filter would be unnecessary. However,...

Can they be negative? Do they have to be integers? I don't really see the advantage of specifying precedence over just filtering in the order the filters are defined. Rather...

I think the unification is a great idea, and I'm trying to incorporate that. However, I think specifying the order your code runs in by a runtime integer rather than...