Ticket #373 (closed task: fixed)
Remodel execution flow
| Reported by: | david | Owned by: | david |
|---|---|---|---|
| Priority: | high | Milestone: | 0.11 |
| Component: | _OTHER_ | Version: | |
| Severity: | blocker | Keywords: | |
| Cc: | Patch attached: |
Description (last modified by david) (diff)
- R.I.P. ActionStack?
- ExecutionContainer? contains info about action, instances, parameters, response etc (pretty much identical to the current ActionStackEntry?)
- Controller::forward() expects a container instance as first argument
- container ctor gets module name, action name, params; action instance is created in initialize()
- forward() calls return a response?
- filter chains, filters, actions, views get this container (instead of the context)
- this should allow decorators inside slots
- if all goes well, we can move decorating out of the renderer back into the view, thus allowing users to do things their way (e.g. use old-style action chaining)
- TBD: how do we store forwards (e.g. when and how is the next action returned by a view executed)
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

