[or-cvs] r16379: Add some pydoc to __init__. (torctl/trunk/python/TorCtl)

mikeperry at seul.org mikeperry at seul.org
Mon Aug 4 10:27:05 UTC 2008


Author: mikeperry
Date: 2008-08-04 06:27:05 -0400 (Mon, 04 Aug 2008)
New Revision: 16379

Modified:
   torctl/trunk/python/TorCtl/__init__.py
Log:

Add some pydoc to __init__.



Modified: torctl/trunk/python/TorCtl/__init__.py
===================================================================
--- torctl/trunk/python/TorCtl/__init__.py	2008-08-04 09:35:20 UTC (rev 16378)
+++ torctl/trunk/python/TorCtl/__init__.py	2008-08-04 10:27:05 UTC (rev 16379)
@@ -1,2 +1,27 @@
+"""
+TorCtl is a python Tor controller with extensions to support path
+building and various constraints on node and path selection, as well as
+statistics gathering.
 
+Apps can hook into the TorCtl package at whatever level they wish. 
+
+The lowest level of interaction is to use the TorCtl module
+(TorCtl/TorCtl.py). Typically this is done by importing TorCtl.TorCtl
+and creating a TorCtl.Connection and extending from TorCtl.EventHandler.
+This class receives Tor controller events packaged into python classes
+from a TorCtl.Connection.
+
+The next level up is to use the TorCtl.PathSupport module. This is done
+by importing TorCtl.PathSupport and instantiating or extending from
+PathSupport.PathBuilder, which itself extends from TorCtl.EventHandler.
+This class handles circuit construction and stream attachment subject to
+policies defined by PathSupport.NodeRestrictor and
+PathSupport.PathRestrictor implementations.
+
+If you are interested in gathering statistics, you can instead
+instantiate or extend from StatsSupport.StatsHandler, which is
+again an event handler with hooks to record statistics on circuit
+creation, stream bandwidth, and circuit failure information.
+"""
+
 __all__ = ["TorUtil", "GeoIPSupport", "PathSupport", "TorCtl", "StatsSupport"]



More information about the tor-commits mailing list