[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5578 [Flashproxy]: Investigate WebRTC for flash proxy NAT punching
#5578: Investigate WebRTC for flash proxy NAT punching
----------------------------+-----------------
Reporter: dcf | Owner: dcf
Type: task | Status: new
Priority: normal | Milestone:
Component: Flashproxy | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
----------------------------+-----------------
Comment (by dcf):
I have some good news. Raymond Cheng from uProxy wrote back and informed
me that the standalone (not browser-embedded) WebRTC source code is
available:
* https://code.google.com/p/webrtc/
* http://www.webrtc.org/webrtc-native-code-package
* http://www.webrtc.org/reference/getting-started
* http://www.webrtc.org/reference/native-apis
*
https://code.google.com/p/webrtc/source/browse/trunk/talk/examples/peerconnection/server
I think this code release is new since we were last looking seriously at
WebRTC.
This is good, because it means we can (probably) implement a WebRTC peer
without involving a browser. It's just a matter of writing a little C++ :)
Proposed plan of attack:
1. Implement a little C++ application and JavaScript program capable of
exchanging data.
2. Somehow merge the prototypes into flashproxy-client and flashproxy.js.
Since #9349 we have the infrastructure in place to allow clients to
register with a "webrtc" transport. I don't see a reason why proxyârelay
communication can't still be "websocket".
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5578#comment:21>
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