It’s been so long since I used orbited that I can’t recall.

Thanks for your tutorial! This helped me learn about how to use Orbited. However, when I tried to use this along with my site built with django, it doesn’t work. The problem is that “stomp.connect(document.domain, 61613); ” doesn’t seem to connect to the stomp server at all (when running the stomp demo, when connect a webpage to the orbited server, there will be a line “ACCESS connection closed from 127.0.0.1:59311 to localhost:61613″ printed in the terminal, but for my site nothing outputed). I have used firebug to dig into the code and find out the code stops running after line 866 of Orbited.js which is “session.open(sessionUrl.render());”. I digged further into .open method for both running stomp demo and my site and didn’t really see differences on the stack.

My guess of the reason is that the stomp demo has the static pages hosted on localhost:9000 which is the same server as the stomp service while my django site is hosted on localhost:8000 and on a different server. But the part confuses me is that when I follow the js code running, I didn’t see any part that can tell whether the page is hosted on orbited server or django server. Have you ever met this situation before?

My understanding of Tornado is that it is a totally different python frame work just like django. I have looked around for about one week but still didn’t figure out how to make Django work with Tornado. Is it something like making django hosted on Tornado or it’s more like the relation between django and orbited – running these two on two servers, let django take care of the logic and let both the webpage and the server send messages to orbited for message passing? Why tornado+django is much easier than orbited+django? Thank you!

Felix

Anyways, two things: the code is cut off in awkward positions, and; process= should be processes=.

Cheers!