Part of twisted.application View Source
Service architecture for Twisted
Services are arranged in a hierarchy. At the leafs of the hierarchy, the services which actually interact with the outside world are started. Services can be named or anonymous -- usually, they will be named if there is need to access them through the hierarchy (from a parent or a sibling).
API Stability: unstable
Maintainer: Moshe Zadka| Line # | Kind | Name | Docs |
|---|---|---|---|
| 24 | Interface | IService | A service. |
| 81 | Class | Service | Base class for services |
| 130 | Interface | IServiceCollection | Collection of services. |
| 171 | Class | MultiService | Straightforward Service Container |
| 237 | Interface | IProcess | Process running parameters |
| 252 | Class | Process | Process running parameters |
| 274 | Function | Application | Return a compound class. |
| 288 | Function | loadApplication | Load Application from file |
Return a compound class.
Return an object supporting theIService,
IServiceCollection, IProcess and
sob.IPersistable interfaces, with the given parameters.
Always access the return value by explicit casting to one of the
interfaces.
| Parameters | filename | (type: str
) |
| kind | (type: str
) | |
| passphrase | (type:
kind, and is one of 'pickle',
'source', 'xml' or 'python'. If passphrase is given, the
application was encrypted with the given passphrase.
) |