public
Description:
Homepage:
Clone URL: git://github.com/carllerche/rack-router.git
joshbuddy (author)
Fri May 29 06:13:35 -0700 2009
commit  4d1f44153a1652aa0d2cde89bdb3952de58dad5a
tree    c0c87038de84629884d521c647c05dad5f76eac5
parent  84fe35d47a02dadc00a605bbbd985339ea5f9f5d
name age message
file .gitignore Thu Mar 26 13:54:26 -0700 2009 Started writing route generation [Carl Lerche]
file LICENSE Thu Mar 26 12:16:58 -0700 2009 Created a gem spec for the project [Carl Lerche]
file README Mon Apr 13 20:22:54 -0700 2009 Refactored the plugin API to accept a simple to... [Carl Lerche]
file Rakefile Thu Apr 30 18:51:55 -0700 2009 Changed the default rake runner to run all spec... [Carl Lerche]
directory benchmarks/ Tue May 05 11:27:53 -0700 2009 Removed path rewriting, it's stupid for the rou... [Carl Lerche]
directory lib/ Fri May 29 06:13:35 -0700 2009 added URI escaping for path parts in generation [joshbuddy]
directory spec/ Fri May 29 06:13:35 -0700 2009 added URI escaping for path parts in generation [joshbuddy]
README
This is my awesome rack router.
Mad props to Josh Peek, a lot (most?) of the concepts come from him.


TODO:

* Freeze the route object when it gets compiled

Some points for discussion:
---------------------------

* Caching the request object
* Passing routing parameters to the app.
  Currently with env['rack_router.params]
* How should an application tell the router that it cannot handle
  the request?
  Currently this is with a custom header
* Should I pass in the matched route in the env
  Currently with env['rack_router.route']
* Should I allow an arbitrary hash to be set on the route (so that you
  can track any information).
* How should multiple request objects be handled in context of mounting.




* Be able to provide route paths using the internal array / string / symbol representation