[tor-dev] Introducing Snowflake (webrtc pt)

[Yawning Angel]

On Mon, 25 Jan 2016 15:32:55 -0800
Serene <keroserene at riseup.net> wrote:

[snip]
> > What are your plans for actually getting the server side to scale
> > well?  Since you're using cgo you will run into Really Interesting
> > behavior wrt OS threads as you try to increase concurrency.  
> 
> Right now, the server side is the same websocket relay from
> flashproxy. Webrtc currently happens just between the client and
> browser proxy - this already yields all the benefits listed above (as
> we assume the volunteer proxy has no problem connecting to Tor)

This seems sensible.

> However, it might be worth having webrtc on both sides. We already
> have prepared a webrtc server plugin, which the client plugin has
> successfully connected to directly. To use a snowflake proxy in
> between would require establishing two separate webrtc peerconnections
> per circuit. Maybe that's worth doing - but I'm not sure about the
> plan there, if we do decide to go that route.

Ah that's what that was.  If you don't use it then, you won't have lots
of misery fighting with cgo's quirks.

Regards,

-- 
Yawning Angel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160125/82a7d1fb/attachment-0001.sig>