removed the request service in favor of the request_stack one
moved everything related to the routing to a reusable service provider
feature #854 [2.0] Request service removal (fabpot)

This PR was merged into the 2.0-experimental branch.

Discussion
----------

[2.0] Request service removal

This one is probably going to be controversial but I'd really think that removing the `request` service is a big step in the right direction.

Giving access to the Request object as a service is wrong for many reasons I won't reiterate here and of course it can cause problems if someone store a reference of it in another service. Instead, the `request_stack` should be injected and the Request object retrieved from it.

If you look at the patch, it's surprisingly easy enough to get rid of it probably because Silex/Symfony are already well aware of that problem (the main changes come from updating the tests).

Commits
-------

e95f7f9 removed the request service in favor of the request_stack one
feature #853 [2.0] moved everything related to the routing to a reusable service provider (fabpot)

This PR was merged into the 2.0-experimental branch.

Discussion
----------

[2.0] moved everything related to the routing to a reusable service provider

The goal is to be able to reuse the router (matcher and generator) outside Silex, but probably in another framework based on Pimple and the Symfony Components.

At this point, I'm not sure if Is it going too far or not. Slowly but steadily, a lot of stuff are migrating to the `Silex\Provider` namespace. That said, I think I'm done with moving things around.

Commits
-------

e5bbc62 moved everything related to the routing to a reusable service provider