No, it's really not that easy, sorry.<p>Looking at the code, you're not actually doing anything with websockets here. There's no handshake parsing, there's no open socket object to pass data back and forth on, there's nothing actually websockety about this.<p>Instead, you seem to have a simple ajax endpoint.<p>Or am I missing something?<p>[EDIT] Clarifying why I said it's not that easy, since that seems snarky as I read it again. To properly do websockets in Django, you have to write your own runserver, which allows processes up the stack to capture the raw socket, perform the websocket handshake methods, and do proper parsing of the incoming data to break the messages on the sentinel values.<p>I recently tried to do this, and the one package that did this wouldn't work with Django 1.6, and we would have to give up our flup runfcgi, which I wasn't ready to do.
This could be useful. A few questions:<p>1) can you describe the tornado part of the system? The blog post isn't really clear on that.<p>2) how do you associate websocket sessions with browser sessions?<p>3) how do you handle server-to-client notifications? ie. a celery task completes and you want to notify the client.<p>4) Is XSS a concern?
This question is more related to websockets. I have seen that they use different protocol and doesn't work behind proxies or firewalls most of the time. How do you handle this?