[py-svn] r6978 - py/dist/doc

[hpk at codespeak.net]

Author: hpk
Date: Sun Oct 17 16:53:47 2004
New Revision: 6978

Modified:
   py/dist/doc/execnet.txt
   py/dist/doc/future.txt
Log:
insert a though reference to the channel api 
(and learned some more ReST :-) 



Modified: py/dist/doc/execnet.txt
==============================================================================
--- py/dist/doc/execnet.txt	(original)
+++ py/dist/doc/execnet.txt	Sun Oct 17 16:53:47 2004
@@ -57,6 +57,8 @@
 The "Channel" interface for exchanging data 
 -------------------------------------------
 
+.. _`channel-api`: 
+
 While executing custom strings on "the other side" is simple enough
 it is often tricky to deal with.  Therefore we want a way
 to send data items to and fro between the distributedly running

Modified: py/dist/doc/future.txt
==============================================================================
--- py/dist/doc/future.txt	(original)
+++ py/dist/doc/future.txt	Sun Oct 17 16:53:47 2004
@@ -314,7 +314,8 @@
 
 We probably want to offer a stripped down functionality of what
 the new `PEP-324 subprocess module`_ offers.  The main functionality 
-of synchronously should have a straightforward api, like:: 
+of synchronously executing [#]_ a system executable should have a 
+straightforward api, maybe:: 
 
     binsvn.execute('ls', 'http://codespeak.net/svn') 
 
@@ -327,6 +328,13 @@
 implementation`_ but would not expose any of its API apart
 from the above "execute()" method. 
 
+.. [#] of course we could also think about replicating the `channel api`_
+       of gateways and return a special ``Channel`` object where you 
+       could call ``receive()`` and ``send()`` on. But these methods 
+       probably don't really fit here. Hum, food for thought. 
+      
+.. _`channel api`: execnet.html#channel-api 
+
 finding an executable
 ---------------------