[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9349 [Flashproxy]: flashproxy facilitator: Allow clients to specify transports
#9349: flashproxy facilitator: Allow clients to specify transports
----------------------------+-------------------
Reporter: asn | Owner: dcf
Type: task | Status: new
Priority: normal | Milestone:
Component: Flashproxy | Version:
Resolution: | Keywords:
Actual Points: | Parent ID: #7167
Points: |
----------------------------+-------------------
Comment (by dcf):
Replying to [comment:12 arlolra]:
> At https://github.com/arlolra/flashproxy/compare/raw, I modified the
standalone flashproxy to terminate the websocket connection and make tcp
connections to generic relays not supporting the websocket pt.
>
> This could be useful for testing the proxy transport chain and the
modified facilitator from #7945.
Thanks for this. I think what we will want to do is build an abstraction
layer for sockets, and then adapt both WebSocket and plain TCP to it.
We're not like to adopt the model where you try to connect to some relay
and then fall back to another transport if it fails. Instead, in #9349 we
let the proxies tell the facilitator what transports they support, and the
facilitator gies them an appropriate relay.
I think the idea of plain TCP between proxy and client is even more
interesting than between proxy and relay.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9349#comment:15>
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