Server Routing
Reported by bahuvrihi | February 16th, 2009 @ 08:35 AM
Routing currently does something like:
/:controller(_controller)/:action
Update this to:
/:controller_key/:action
Such that using escapes you can specify a minikey for any constant.
/app/:action # => App
/tap-server%3aapp/:action # => [tap-server] App
/tap-server%3apath%2Fto%2Fapp/:action # => [tap-server] Path::To::App
In this case env.controllers can become a 'standard' manifest and controllers can be put anywhere and marked by a '::controller' const_attr. What's more this makes view paths simpler with a single rule: 'views/path/to/const'
Comments and changes to this ticket
-
bahuvrihi March 4th, 2009 @ 08:20 PM
Maybe specify a good way to forward requests as well... tasks are often named very well so it would be useful if there were a way to add a task controller without beating on the actual constant.
- option one: if a constant doesn't have a call method, then look for ConstantController.
- option two: have the task define call that calls TaskController
Option one is not only slicker but it also keeps controller logic completely out of tasks.
-
bahuvrihi May 25th, 2009 @ 11:58 AM
- State changed from “new” to “invalid”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi