Optimized table based routing and changed its behavior to a more consistent one.

[manast]

"pizza.com/taco/muffins": "127.0.0.1:8099' -> 127.0.0.1:8099
"pizza.com/taco/muffins": "127.0.0.1:8099/pasta/tomato' -> 127.0.0.1:8099/pasta/tomato

[manast]

It passes current unit tests but I could not write new unit tests for testing my specifics since I get an error if I do so which I have not yet figured out how to fix:

Error: EADDRINUSE, Address already in use

[max-mapper]

@manast the test harness starts a separate single-use proxy for each entry in the proxytable and each proxy must have a unique port as per the way the test harness is implemented

[manast]

@maxogden well, that was what I thought, but it seems as I never manage to find any port that is not already busy, because it keeps failing :/

[manast]

well, for me it is insane, I can not manage to make it working and unfortunately I have to move on to other things... in order to make this unit tests scalable (right now I think there is far too few tests to say that this is production ready), it is needed a better approach than trying to figure out which ports are free by hand, maybe we could use a function that returns a unique port every time it is called or something, then we need to match that port in the tests later on...

[coderarity]

Oops, seems like I did this again at #218. Not sure why there's so many more changes in your version though.

[indexzero]

There have been a bunch of changes to this in master. If you're still having the same issue when we release the new version feel free to reopen.