Home | Trees | Indices | Help |
---|
|
Exchange --+ | Map
An exchange which can be used like the built-in 'map' function.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
Initialise the exchange with an optional list of 'channels'. If the optional 'limit' is specified, restrictions on the addition of new channels can be enforced and observed through the 'add_wait', 'wait' and 'finish' methods. To make use of these methods, create a subclass of this class and define a working 'store_data' method. If the optional 'reuse' parameter is set to a true value, channels and processes will be reused for waiting computations, but the callable will be invoked for each computation. If the optional 'continuous' parameter is set to a true value, channels and processes will be retained after receiving data sent from such processes, since it will be assumed that they will communicate more data. If the optional 'autoclose' parameter is set to a false value, channels will not be closed automatically when they are removed from the exchange - by default they are closed when removed.
|
Add the given 'channel' to the exchange.
|
Create a new process for the given 'callable' using any additional arguments provided. Then, monitor the channel created between this process and the created process.
|
Create a new process and return the created communications channel to the created process. In the creating process, return None - the channel receiving data from the created process will be automatically managed by this exchange.
|
Accumulate the incoming data, associating results with channels.
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Thu Dec 12 18:55:51 2013 | http://epydoc.sourceforge.net |