Home | Trees | Indices | Help |
|
---|
|
object --+ | base.structure.StructureBase --+ | object --+ | | | base.common.Parser --+ | base.structure.ParseableStructure --+ | base.structure.Structure --+ | object --+ | | | base.structure.RestrictionMixin --+ | rscdef.procdef.ProcDef --+ | rscdef.procdef.ProcApp --+ | DataFormatter
A procedure application that renders data in a processed service.
These play the role of the renderer, which for datalink is ususally trivial. They are supposed to take descriptor.data and return a pair of (mime-type, bytes), which is understood by most renderers.
When no dataFormatter is given for a core, it will return descriptor.data directly. This can work with the datalink renderer itself if descriptor.data will work as a nevow resource (i.e., has a renderHTTP method, as our usual products do). Consider, though, that renderHTTP runs in the main event loop and thus most not block for extended periods of time.
The following names are available to the code:
In addition to the usual names available to ProcApps, data formatters have:
Nested Classes | |
Inherited from |
Instance Methods | |
Inherited from Inherited from Inherited from Inherited from Inherited from Inherited from Inherited from |
Class Methods | |
Inherited from |
Class Variables | |
name_ =
hash(x) |
|
requiredType =
hash(x) |
|
formalArgs =
|
|
additionalNamesForProcs = {"Page": rend.Page, "IRequest": inev
|
|
Inherited from Inherited from Inherited from |
Properties | |
Inherited from |
Class Variable Details |
additionalNamesForProcs
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Thu May 2 07:29:09 2019 | http://epydoc.sourceforge.net |