Having routes in the Pool

[ced (Cédric Krier)]

@nicoe

• Adding a new type in the Pool: route
• Objects will be registered in the Pool by their __name__

I think those objects should be named router and Router .

@nicoe

Just like we register methods in __rpc__, those object will contain a mapping named __routes__ between a couple (endpoint, HTTP Verb) and a Route object

I think it will be better to use the method name as key and a list of decorator as value.

@nicoe

At the end of the initialization of a database pool a process will define in Werkzeug all the available routes.

We need to remove the routes on Pool.stop.

@nicoe

The URL will be composed as follow: /<database>/<__name__>/<endpoint>

I think it will be good to have a fixed prefix before <__name__> as we have now already rpc and rest.

@nicoe

It might happen that a request to a route will be the event that initialize the pool (and thus the routes are not known yet), in this case instead of raising a 404, we should initialize the pool and then replay the request.

It is probably simpler to have a catch all route for any database and all the possible route and return a 503 with a Retry-After and initialize the pool.