Resource matcher routing (rewrite)

[Ocramius]

Supersedes #72

• Moving matching of associations (and generic hops in the URL) to a recursive matcher that assembles a SubPathMatch object
• Moving single types of match to own sub-path matchers
• Consider using the "part" route for sub-paths
• Producing a SubPathMatch with all previous sub-path matches in it
• Assembling of a full URL from a given SubPathMatch
• Pluggable collection filtering logic (when reaching the path's end, if the leaf is a collection, it may be filtered based on custom rules)
• Tests

[bakura10]

Is this check really needed ? It's already taken care in the BaseSubPathMatcher.

[Ocramius]

I don't assume this will always be used with the BaseSubPathMatcher

[bakura10]

Looks good otherwise :). Please, when you'll plug this to the ResourceGraphRoute, rename it to RestResourceRoute also while you're at it ;-).

[bakura10]

I'm taking this branch. I'm refactoring ZfrRest right now in this branch: https://github.com/zf-fr/zfr-rest/tree/voltaire

I've taken your code, added some things and currently writing tests for it. So I will close yours.

[bakura10]

@Ocramius : regarding the filtering issue, here is how I did it: https://github.com/zf-fr/zfr-rest/blob/voltaire/src/ZfrRest/Mvc/Router/Http/Matcher/CollectionSubPathMatcher.php#L149-L158

Using events seems the only flexible way to be able to implement custom logic. What do you think?