gavo.protocols package¶
Submodules¶
- gavo.protocols.adqlglue module
- gavo.protocols.creds module
- gavo.protocols.dali module
- gavo.protocols.datalink module
- gavo.protocols.datapack module
- gavo.protocols.dlasync module
- gavo.protocols.gavolog module
- gavo.protocols.linetap module
- gavo.protocols.oaiclient module
- gavo.protocols.obscore module
- gavo.protocols.products module
- gavo.protocols.scs module
- gavo.protocols.sdm module
- gavo.protocols.siap module
- gavo.protocols.simbadinterface module
- gavo.protocols.soda module
- gavo.protocols.ssap module
- gavo.protocols.tap module
- gavo.protocols.taprunner module
- gavo.protocols.useruws module
- gavo.protocols.uws module
- gavo.protocols.uwsactions module
- gavo.protocols.vocabularies module
Module contents¶
IVOA, W3C, and custom protocol helpers (in cooperation with twisted-based code in weg).
The guiding line should be: Stuff that depends on twisted should go to web or svcs, generic code should be here. Of course, these rules are constantly bent.
When writing support for a protocol, do as much as possible as far as templates for RDs in an RD //<protoname>.
Use the code in protocols for the core and possible library-like functionality.