Allow one deferred to run pending the result of another
Registered by
Christopher D. Leary
The general specification for chaining deferreds together is given at the URI in the "Chaining Deferreds" section. The idea is that a single asynchronous "task" -- as represented by a deferred -- may consist of several subsequent pieces of asynchronous I/O -- also represented as deferreds -- which must be "chained together".
Blueprint information
- Status:
- Not started
- Approver:
- Christopher D. Leary
- Priority:
- Essential
- Drafter:
- Christopher D. Leary
- Direction:
- Approved
- Assignee:
- Christopher D. Leary
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Modified deferred interface to mimic the Twisted version -- this allows decoupling of the stage descriptor/host controller driver from the deferred interface. The deferred completion will be moved to some object which is shared across stage descriptors and waits for a certain number of stage descriptors to complete (whether successfully or unsuccessfully).
(?)
