[tor-commits] [flashproxy/master] Remove some more references to Adobe Flash.

[dcf at torproject.org]

commit 32c5609ab34f00e6ef92b75e37c68fe1d4b6386e
Author: David Fifield <david at bamsoftware.com>
Date:   Wed Jul 4 08:16:52 2012 -0700

    Remove some more references to Adobe Flash.
---
 README         |    8 +++-----
 doc/design.txt |   18 ++++++++----------
 facilitator.py |    3 ---
 3 files changed, 11 insertions(+), 18 deletions(-)

diff --git a/README b/README
index 71fbffe..8b7e9b5 100644
--- a/README
+++ b/README
@@ -2,8 +2,7 @@
 
 This is a set of tools that make it possible to connect Tor through an
 browser-based proxy running on another computer. The flash proxy can be
-run just by opening a web page in a computer that has Flash Player
-installed.
+run just by opening a web page in a browser.
 
 There are five main parts. Our terminology for each part is in quotes.
 1. The Tor "client," running on someone's localhost.
@@ -46,9 +45,8 @@ if you are able to configure port forwarding or receive direct
 connections from the Internet.
 
 If you don't get a connection within 30 seconds or so, make sure someone
-with Flash Player is viewing http://crypto.stanford.edu/flashproxy/.
-There aren't yet enough operational proxies that one is available all
-the time.
+is viewing http://crypto.stanford.edu/flashproxy/. There aren't yet
+enough operational proxies that one is available all the time.
 
 === Direct TCP connection
 
diff --git a/doc/design.txt b/doc/design.txt
index ecee83c..c8141dd 100644
--- a/doc/design.txt
+++ b/doc/design.txt
@@ -19,16 +19,14 @@ Design of flash proxies
   temporary and short-lived, but their number will be great enough that
   they can't all be blocked effectively.
 
-  The implementation of a browser-based proxy using Adobe Flash or other
-  networking technologies is complicated by restrictions that prevent it
-  being a straightforward proxy. Chief among these is the lack of
-  listening sockets. Flash and, for example, WebSockets, can only
-  initiate outgoing connections, not receive incoming ones. The flash
-  proxy can only connect to external hosts by connecting directly to
-  them. The other significant restriction is that the proxy cannot
-  connect to just any destination. A third, but less important,
-  restriction is that browser-based networking does not provide
-  low-level socket access such as control of source address.
+  The implementation of a browser-based proxy using WebSocket is
+  complicated by restrictions that prevent it being a straightforward
+  proxy. Chief among these is the lack of listening sockets. WebSocket
+  can only initiate outgoing connections, not receive incoming ones. The
+  flash proxy can only connect to external hosts by connecting directly
+  to them. Another, but less important, restriction is that
+  browser-based networking does not provide low-level socket access such
+  as control of source address.
 
 2. Components
 
diff --git a/facilitator.py b/facilitator.py
index 64de7a6..2a04e71 100755
--- a/facilitator.py
+++ b/facilitator.py
@@ -253,9 +253,6 @@ class Handler(BaseHTTPServer.BaseHTTPRequestHandler):
         if reg:
             client_str = str(reg)
         else:
-            # Send an empty string rather than a 404 or similar because Flash
-            # Player's URLLoader can't always distinguish a 404 from, say,
-            # "server not found."
             client_str = ""
         self.send_response(200)
         self.send_header("Content-Type", "application/x-www-form-urlencoded")