Arlo Breault
|
598e2a3bfb
|
Close SocksConn when WebRTC connection is reset
* This will induce the tor client to establish a new SocksConn,
which in turn will dial a new WebRTC connection.
To be improved upon.
* Part of #12
|
2016-03-18 21:29:31 -07:00 |
|
Serene Han
|
ba7b59f80e
|
clarify webRTCConn errorChannel and error handling
|
2016-03-10 17:14:45 -08:00 |
|
Serene Han
|
f91b8faa0a
|
more informative broker error messages (close #26)
|
2016-03-09 14:37:45 -08:00 |
|
Serene Han
|
960a136c64
|
retry client offers immediately instead of reset, combine sendOffer and receiveAnswer into exchangeSDP
|
2016-03-08 20:33:39 -08:00 |
|
Serene Han
|
91673a4abe
|
fix datachannel remote vs. local closing during client's peerconnection cleanup
|
2016-03-06 11:40:05 -08:00 |
|
Serene Han
|
5edac195f6
|
move endWebRTC() mostly into webRTCConn.Close()
|
2016-02-26 14:35:20 -08:00 |
|
Serene Han
|
f3e0abe0e1
|
only flush datachannel with nonzero bytes, which prevents Tor from marking the SOCKS for close (#12)
|
2016-02-25 01:24:06 -08:00 |
|
Serene Han
|
d4efe774d1
|
remove webRTCConn SendLoop and simplify Write without additional channel, as net.Conn is already safe
|
2016-02-23 17:34:51 -08:00 |
|
Serene Han
|
3a7e0ea620
|
simplify client handler & dialWebRTC with independent webRTCConn constructor
|
2016-02-23 17:01:44 -08:00 |
|
Serene Han
|
f86f5b5b07
|
move webRTCConn into separate file
|
2016-02-21 22:03:19 -08:00 |
|