#2165: Refactor dispatch
------------------------+---------------------------------------------------
Reporter: percious | Owner: percious
Type: defect | Status: new
Priority: normal | Milestone: 2.0
Component: TurboGears | Version: trunk
Severity: normal | Keywords: dispatch routes
------------------------+---------------------------------------------------
Dispatch currently resides as a large set of cascaded functions. There is
only one method for dispatch and it cannot be overridden by the developer.
I'm proposing that all dispatch method is encapsulated inside
ObjectDispatch and RestDispatch, allowing developers to create their own
custom dispatch. It works like this:
Dispatch begins with the RootController, which is always Object Dispatch.
Then, the dispatch is passed off to each Dispatch object in turn.
Dispatch continues down the branches of the URL. At each branch, dispatch
will detect if the next object in the chain has it's own dispatcher, and
if it does, the method of dispatch continues on with this new method.
Along the way, a chain of controller object references is kept in-memory
so that any time the dispatch can see how it got where it is.
This will be backwards-compatible, and allow for people to develop their
own different kinds of dispatch.
I expect this to be completed during PyCon 2009.
--
Ticket URL: <http://trac.turbogears.org/ticket/2165>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
