Re: Running Django and a socket server

Hello Ralf, A possible third option would be to bypass using sockets and use something like XML-RPC instead (which can still use the same server running) and have your 'client' issue XML-RPC requests. There's a Google code project that makes this absolutely trivial through Django, http://code.goo

Re: Running Django and a socket server

> > If you plan on communicating between these two types of services over > TCP sockets, I don't see why that would be easier with option #2 than > with option #1. Socket communication shouldn't have to care if the end > points of the socket belong to the same process or two different > processe

Re: Running Django and a socket server

Hi, > I'm creating an application containing two interfaces: a socket server > and a web interface. Both interfaces require access to the same > database, and there will be a small amount of communication between > the two interfaces. > > I want to use Django for the web interface, as well as the

Running Django and a socket server

Hi, I'm creating an application containing two interfaces: a socket server and a web interface. Both interfaces require access to the same database, and there will be a small amount of communication between the two interfaces. I want to use Django for the web interface, as well as the ORM for th