[Twisted-Python] Re: async code structure question

Mary Gardiner mary-twisted at puzzling.org
Thu Feb 10 17:48:47 EST 2005

On Thu, Feb 10, 2005, David Bolen wrote:
> Alternatively, the authorization class/code can just make its own
> deferred (either directly or by performing a deferred operation) and
> returns it to its caller.  The caller of authorize then sees it as a
> deferable operation (returning a deferred) onto which it can hang any
> callbacks, which which might be as simple as chaining to the initial
> deferred.

True. It's generally a good idea to have a distinction between the
library code which returns various Deferreds, and application code which
adds callbacks to them in order to feed the data around in the right
order and then act depending on the result.


More information about the Twisted-Python mailing list