"In computer programming, the adapter design pattern (often referred to as the wrapper pattern or simply a wrapper) translates one interface for a class into a compatible interface. An adapter allows classes to work together that normally could not because of incompatible interfaces, by providing its interface to clients while using the original interface. The adapter translates calls to its interface into calls to the original interface, and the amount of code necessary to do this is typically small. The adapter is also responsible for transforming data into appropriate forms."
—Wikipedia page on the adapter pattern
In this project, this pattern has been formalized by the use of the zope.interface and zope.component packages. zope.interface prvides a method to formally define interfaces independent of their implementations, and zope.component facilitates the creation and registration of adapters when they are necessary.
You can find more information on the Zope Component Architecture and it's adapter system by reading A Comprehensive Guide to Zope Component Architecture by Baiju M, in particular chapter 4, as well as in the documentation for the zope.interface and zope.component packages. For more general information about adapters, see the Wikipedia page on the adapter pattern.
Todo
Document term Backplane
Todo
Document term Component
Todo
Document term Concurrent
Todo
Document term Consumer
Todo
Document term Container
"A coroutine is a generalization of the subroutine. Forget for a moment everything you've been taught about calling functions, and stacks, etc... Think back to BASIC, and the evil GOTO statement. Imagine a more powerful GOTO that could jump back and forth between functions, passing arguments, and you begin to get the idea."
"Coroutines are a bit of ancient forgotten computer-science lore; stamped out of the collective memory by the hegemony of C. But they are useful in a wide variety of situations that can only be clumsily solved using 'standard' tools like threads and processes."
Coroutines in Python are described in PEP 342. There is an excellent presentation on Python coroutines titled A Curious Course on Coroutines and Concurrency by David Beazley. For information on coroutines in general, see the Wikipedia page on coroutines.
Todo
Document term Factory
Todo
Document term Filter
"A generator is, simply put, a function which can stop whatever it is doing at an arbitrary point in its body, return a value back to the caller, and, later on, resume from the point it had 'frozen' and merrily proceed as if nothing had happened."
Generators in Python are described in PEP 255. There is an excellent presentation on Python generators titled Generator Tricks for Systems Programmers by David Beazley. For information on generators in general, see the Wikipedia page on generators.
Todo
Document term idempotent
Todo
Document term Inbox
Todo
Document term Interface
Todo
Document term Lazy
Todo
Document term Link
Todo
Document term Mailbox
Todo
Document term Message
Todo
Document term Outbox
Todo
Document term Pipeline
Todo
Document term Post Office
Todo
Document term Publisher
Todo
Document term Scheduler
Todo
Document term Sink
Todo
Document term Source
Todo
Document term Subscriber