<br><br><div class="gmail_quote">On Wed, Aug 15, 2012 at 5:36 PM, Thomas Kluyver <span dir="ltr"><<a href="mailto:takowl@gmail.com" target="_blank">takowl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 16 August 2012 01:32, Darren Govoni <<a href="mailto:darren@ontrenet.com">darren@ontrenet.com</a>> wrote:<br>
> Is it because the websockets that use the random ports? I presume there is<br>
> no kind of "proxy" or tunneling for websockets<br>
> to deal with secure environments?<br>
<br>
</div>As I understand it, websockets themselves go over port 80. But then<br>
the notebook server forwards the data to the kernel over a ZMQ socket,<br>
which is using the arbitrary ports.<br></blockquote><div><br></div><div>Yes, it's not the websockets - it's the notebook server talking to the kernels over ØMQ, where the code is actually running.</div><div>On Windows, you simply need to be able to open numerous loopback ports for this to work. There is no alternative. There *is* an alternative on platforms other than Windows (IPC).</div>
<div><br></div><div>-MinRK</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Thomas<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
IPython-User mailing list<br>
<a href="mailto:IPython-User@scipy.org">IPython-User@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-user" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-user</a><br>
</div></div></blockquote></div><br>