gavo.protocols package

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.