Home | Trees | Indices | Help |
|
---|
|
object --+ | base.structure.StructureBase --+ | object --+ | | | base.common.Parser --+ | base.structure.ParseableStructure --+ | base.structure.Structure --+ | Core
A definition of the "active" part of a service.
A core will receive input from a renderer in the form of a ``svcs.CoreArgs`` (see `Core Args`_). A core will return a table or perhaps directly data as discussed in `DaCHS' Service Interface`_ .
The abstract core element will never occur in resource descriptors. See `Cores Available`_ for concrete cores. Use the names of the concrete cores in RDs.
Nested Classes | |
Inherited from |
Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from Inherited from Inherited from Inherited from Inherited from |
Class Methods | |
Inherited from |
Class Variables | |
name_ =
a sentinel for all kinds of undefined values. |
|
inputTableXML = None hash(x) |
|
outputTableXML = None hash(x) |
|
attrSeq =
|
|
managedAttrs =
|
|
Inherited from Inherited from |
Properties | |
rd | |
Inherited from |
Method Details |
x.__init__(...) initializes x; see help(type(x)) for signature
|
repr(x)
|
str(x)
|
|
override to configure the custom core before use. This is typically where you pull input or output tables from the RD in customCores. Actual DaCHS code should use completeElement as usual. |
Class Variable Details |
attrSeq
|
managedAttrs
|
Property Details |
rd
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Thu May 2 07:29:09 2019 | http://epydoc.sourceforge.net |