   A router is the heart of a Phoenix application. It has three
   main responsibilities:
 
-    * It provides routes and named route conveniences for
-      routing requests to controllers
-
-    * It defines a plug pipelines responsible for handling
-      upcoming requests
+    * It defines a plug pipeline responsible for handling
+      upcoming requests and dispatch those requests to
+      controllers and other plugs
 
     * It hosts configuration for the router and related
       entities (like plugs)
 
-    * It provides a wrapper for starting and stopping a
-      web server specific to this router
+    * It provides a wrapper for starting and stopping the
+      router in a specific web server
 
   We will explore those responsibilities next.
 

          config :phoenix, YourApp.Router,
            session: [store: :cookie, key: "_your_app_key"]

    * `:parsers` - sets up the request parsers. If parsers are disabled,
      parameters won't be explicitly fetched before matching a route and
      functionality dependent on parameters, like the `Plug.MethodOverride`,
      will be disabled too. Defaults to:

          [accept: ["*/*"],
           json_decoder: Poison,
           parsers: [:urlencoded, :multipart, :json]]

    * `:static` - sets up static assets serving. Defaults to:

          [at: "/",
           from: Mix.Project.config[:app]]

  ### Runtime

    * `:http` - the configuration for the http server. Defaults to:

          [port: 4000]

    * `:https` - the configuration for the https server. Defaults to:

          [port: 4040]

    * `:secret_key_base` - a secret key used as base to generate secrets
      to encode cookies, session and friends. Defaults to nil.

    * `:url` - configuration for generating URLs throughout the app. Defaults to:

          [host: "localhost"]

  ## Web server

  TODO: documentation.

  """

  alias Phoenix.Plugs

        plug :token_authentication
      end

  Where `plug :super` will invoke the existing pligs in the api
  pipeline. In general though, it is preferred to define new pipelines
  then modify existing ones.

  ## Router configuration

