Changes between Version 1 and Version 2 of Ticket #9349, comment 25


Ignore:
Timestamp:
Sep 19, 2013, 6:32:41 PM (6 years ago)
Author:
infinity0
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9349, comment 25

    v1 v2  
    22> `options.relays` should be indexed not by complete transport chains, but by transport chains excluding their last element. It should be possible for an obfs3|websocket client to talk to an obfs3|tcp relay, if there is a proxy that speaks both websocket and tcp. To be specific you should key by the tuple `("obfs3",)` and not `("obfs3", "websocket")`.
    33>
    4 As I understand it, this would require additional changes on the client side to parse the response from the facilitator and initiate connections via the correct engines (when we finally do support more than 2 types of relay e.g. out of websocket/webrtc/plain-tcp). At the moment the client only sends "transport=websocket", it doesn't parse the response and assumes websocket-websocket proxying.
     4As I understand it, this would require additional changes on the client side to parse the response from the facilitator and initiate connections via the correct engines (when we finally do support more than 2 types of relay e.g. out of websocket/webrtc/plain-tcp). At the moment the proxy only sends "transport=websocket", it doesn't parse the response and assumes websocket-websocket proxying.