Lifecycle hooks on routes

[Marsup]

What would you think of allowing the lifecycle hooks (all but onRequest obviously) to be set per route ?
The filtering I have to do to match routes in those functions just pollutes the readability of it.
Having global hooks when they're not used as such probably also is a tiny waste of resource however minor.

[hueniverse]

I've long wanted to change the ext functionality to be per:

• server
• connection
• plugin
• route

But I am worried about the overhead of checking for all those. Right now when nothing is set it is a simple null check at each ext point. For this to work I will need to change the lifecycle array generation to actually build the array per route as well as rebuild it when extensions are added later after route config.

Maybe for 9.0.

[devinivy]

This would be wonderful. @hueniverse are you worried about overhead at the time of server start, or throughout the course of a single request?

[hueniverse]

Only care about hot code. Executing the request lifecycle is hot.

[seanrucker]

Looking forward to this feature; here's my use case...

I'm using Hapi as an API Gateway. I have four clients accessing this API, each has its own set of routes. One of the clients is an Ember app which requires the API response to conform to the JSON API spec. I'm using a Hapi plugin (inspired by hapi-json-api.js) to handle some of the boilerplate code required to munge the response into something JSON API compliant. The plugin uses Hapi lifecycle hoks which unfortunately has the effect of making all my routes conform to JSON API.

[hueniverse]

What would the interface look like for adding extensions to one or more routes? I got ideas but want to see what other people think.