doc: updates to route_matching section
Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>
This commit is contained in:
@@ -20,10 +20,10 @@
|
||||
theory/philosophy
|
||||
theory/request_life_cycle
|
||||
theory/resource_tree
|
||||
theory/route_matching
|
||||
theory/routes
|
||||
|
||||
|
||||
|
||||
Indices and tables
|
||||
==================
|
||||
|
||||
|
||||
@@ -1,12 +1,14 @@
|
||||
Route Matching
|
||||
==============
|
||||
|
||||
Route table
|
||||
-----------
|
||||
Kapow! maintains a route table with a list of routes as provided by the user,
|
||||
and uses it to determine which handler should an incoming request be dispatched
|
||||
to.
|
||||
|
||||
Kapow! maintains a route table as provided by the user, and uses it to determine
|
||||
which handler should an incoming request be dispatched to.
|
||||
.. todo::
|
||||
|
||||
Each incoming request is matched against the routes in the route table in
|
||||
strict order, for each route in the route table, the criteria are checked.
|
||||
If the request does not match, the next route in the route list is examined.
|
||||
link routes to its section
|
||||
|
||||
Each incoming request is matched against the routes in the route table in
|
||||
strict order, for each route in the route table, the criteria are checked.
|
||||
If the request does not match, the next route in the route list is examined.
|
||||
|
||||
Reference in New Issue
Block a user