1 """
2 IVOA, W3C, and custom protocol helpers (in cooperation with twisted-based
3 code in weg).
4
5 The guiding line should be: Stuff that depends on nevow (or even twisted)
6 should go to web or svcs, generic code should be here. Of course, these
7 rules are constantly bent.
8
9 When writing support for a protocol, do as much as possible as far as
10 templates for RDs in an RD //<protoname>.
11
12 Use the code in protocols for the core and possible library-like functionality.
13 """
14
15
16
17
18
19
20
21
22