Support next() across multiple routes

[frenzzy]

need help with fix

[langpavel]

@frenzzy Can you describe more?

[frenzzy]

Sure, I found two problems:

1. resolve() traverses all list of routes until one of them will return something, but next() function matches only single next route although it should traverses the remaining routes until one of them does not return something.
   • How to solve: move the traverse code in the next function.
   • It allows to remove this code from RSK.
2. Traversing routes must be strictly sequential and not parallel (similar to express.js). Bug: at the moment the router returns the result of the fastest asynchronous route instead of returning the result first of them.
   • Problem place: resolve.js#L51-L57

[langpavel]

Ahhh, this looks like BIG issue, maybe bug..?

I don't like loop in RSK, it's potential source of DoS attack.. :-\

[coveralls]

Coverage decreased (-0.3%) to 88.235% when pulling 96e594b on frenzzy:next-multiple-routes into 9740ad0 on kriasoft:master.