<p>Much as with Ruby on Rails, Turbinado uses “routes” to direct traffic to particular Controllers. Routes are configured in <a href="http://github.com/alsonkemp/turbinado-website/tree/master/Config/Routes.hs.sample">Config/Routes.hs</a>. A sample set of routes is in <a href="http://github.com/alsonkemp/turbinado-website/tree/master/Config/Routes.hs.sample">Config/Routes.hs.sample</a>, which contains:</p>
<pre>
module Config.Routes where
routes = [ "/:controller/:action/:id"
, "/:controller/:action.:format"
, "/:controller/:action"
, "/:controller"
]
</pre>
<p>Using these routes, a request to<br />
<pre><br />
/Page/Show/title<br />
</pre><br />
would:</p>
<ol>
<li>Insert into the Settings:<br />
o “controller” => “Page”<br />
o “action” => “Show”<br />
o “id” => “title”</li>
<li>Invoke the “show” function in /App/Controllers/Page.hs. Presumably, the controller would want to getSetting “id”.</li>
<li>Invoke the “markup” function in /App/Views/Page/Show.hs</li>
</ol>
2009-11-25T15:03:42-08:00
236272
architecture-routes
76548
Architecture - Routes
2009-06-09T17:48:57-07:00
34693