Shows how to add routes which can serve multiple content types using strict content-type negotiation.
Basically, the Accept header is checked against the list of supplied services and a match found. If there is no
Accept header set in the request, the first service in the list is used. This means that there is NO sophisticated
content negotiation implemented, although Wildcard Accept headers is supported to match the first supplied mapping service.
(Since version 2.11.0) The delayedInit mechanism will disappear.