Re: Does Django support sockets of type SOCK_STREAM for full-duplex communication with a client?

You can fun a separate process to do this. It should probably be written as a manage.py extension to make access to the DB via the ORM as painless as possible. This way the web server thread is not tied up and can handle requests. The saves to the database (that I presume you're not showing)

Re: Does Django support sockets of type SOCK_STREAM for full-duplex communication with a client?

Hello Chris, On Mon, Dec 21, 2009 at 04:49:56PM -0800, Chris wrote: > I have a client that needs to constantly send data to Django-based > backend. The client code follows the pattern: > > ... > s = socket.socket( socket.AF_INET, socket.SOCK_STREAM ) > s.connect( ( '10.20.30.40', 8080 ) ) >

Re: Does Django support sockets of type SOCK_STREAM for full-duplex communication with a client?

On Dec 22, 2:49 am, Chris wrote: > Hello, > > I have a client that needs to constantly send data to Django-based > backend. The client code follows the pattern: > > ... > s = socket.socket( socket.AF_INET, socket.SOCK_STREAM ) > s.connect( ( '10.20.30.40', 8080 ) ) > while

Does Django support sockets of type SOCK_STREAM for full-duplex communication with a client?

Hello, I have a client that needs to constantly send data to Django-based backend. The client code follows the pattern: ... s = socket.socket( socket.AF_INET, socket.SOCK_STREAM ) s.connect( ( '10.20.30.40', 8080 ) ) while True : data = s.recv( 2048 ) print data s.send(