<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>According this page, <a href="http://ipython.org/ipython-doc/stable/development/messaging.html">http://ipython.org/ipython-doc/stable/development/messaging.html</a></div><div>Most of the default channels are used by the kernel for particular purpose. Are you suggesting to overload the shell sockets for extra communication? If so, I can look into how to do that.</div><div><br></div><div><br><div><div>On Feb 13, 2012, at 5:09 PM, Brian Granger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I don't think you need to add an additional WebSocket channel for any<br>purpose. Of course your Javascript widgets are free to talk to *any*<br>WebSocket server in the world, including a modified IPython notebook<br>server. But as long as you want to talk to your Python code in the<br>backend, you should just use our existing channels.<br><br>On Mon, Feb 13, 2012 at 4:03 PM, Chen-Shan Chin <<a href="mailto:cschin@infoecho.net">cschin@infoecho.net</a>> wrote:<br><blockquote type="cite">Yes. It will nice to use the ipython architecture for interactive<br></blockquote><blockquote type="cite">stuff. Let's say if I create a javascript widget, and I want to send the<br></blockquote><blockquote type="cite">event to a user defined function/method, what is the best way to do that?<br></blockquote><blockquote type="cite">What I think is to have a auxiliary websocket-zmq bridge for this purpose.<br></blockquote><blockquote type="cite"> Does it make sense?<br></blockquote><blockquote type="cite"><br></blockquote><br class="Apple-interchange-newline"></blockquote></div><br></div></body></html>