[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #7687 [Stem]: RFC: add close_stream method to Controller



#7687: RFC: add close_stream method to Controller
-------------------------------+--------------------------------------------
 Reporter:  robinson           |          Owner:  atagar
     Type:  enhancement        |         Status:  new   
 Priority:  normal             |      Milestone:        
Component:  Stem               |        Version:        
 Keywords:  controller stream  |         Parent:        
   Points:                     |   Actualpoints:        
-------------------------------+--------------------------------------------
 Damian,

 I have finally settled on what I think is a reasonable approach to
 StreamClosureReason (SCR) and RelayEndReason (RER) enums.  But I am still
 working on tests for close_stream, so RFC for now.

 1) Does my handling of the *Reason enums work for you?  My research in the
 tor source and torspec indicates that the reasons the tor process sends in
 the STREAM event are direct mappings of the reason the relay ended.
 Except, with STREAM (FAILED|CLOSED|DETACHED), REASON=END and the "real"
 reason is in REMOTE_REASON.

 2) How do you feel about adding the SocksiPy
 <http://sourceforge.net/projects/socksipy/> module under test/ ?  This is
 a BSD-licensed module that I hope will make stream-using integ tests
 possible.  But I have not yet tried, so maybe it won't help.

 This work is in the exp-close-stream-v1 branch on git://gitorious.org
 /stem-robinson/stem-robinson.git and commit logs can be read at
 https://gitorious.org/stem-robinson/stem-robinson/commits/exp-close-
 stream-v1

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7687>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs