\n\n\n" }Most routing systems combine the \u00e2\u0080\u009crouting\u00e2\u0080\u009d task with the \u00e2\u0080\u009cdispatch\u00e2\u0080\u009d task. That is, they both extract the parameters and pick the controller/action. Aura.Router v2, because of its truly independent nature, only does routing. It turns out that dispatching is something that can be independent of routing, and so we have a separate Aura.Dispatcher package to handle that (although you can use any dispatching system you like).
\n\u2026
\nAura.Router v2 allows you to examine the $_SERVER values and pick a route based on them using the addServer() method. For example, if you want to match routes based on the HTTP_ACCEPT value \u00e2\u0080\u00a6
\n\n<?php\n$router->addRoute('json_only', '/accept/json/{id}')\n->addServer(array(\n // must be of quality *, 1.0, or 0.1-0.9\n 'HTTP_ACCEPT' => 'application/json(;q=(*|1.0|[0.[1-9]]))?'\n));\n?>\n\u2026
\nSometimes we need a params in the route path to be sequentially optional. The classic example is a blog archive organized by year, month, and day. We don\u00e2\u0080\u0099t want to have to write three routes, one for /{year}, /{year}/{month}, and /{year}/{month}/{day}, each with repeated information about the route.
\nIn Aura.Router v2, there is a special notation similar to URI Templates that indicates sequentially optional params:
\n{/param1,param2,param3}\u2026
\nWe can now add REST resource routes in a single call to attachResource():
\n\n<?php\n$router->attachResource('blog', '/blog');\n?>\nThis will add seven REST routes with appropriate names, paths, HTTP methods, and token regexes \u2026
\nIf you decide those routes are not to your liking, you can override the default behavior by using setResourceCallable() to pass callable of your own to create resource routes.
\n