Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a Django application which sometimes needs to send some data through TCP and I want this connection to be persistant.
The way I wanted to do it was to create a simple Twisted TCP server (I’m the one who will be waiting for the initial connection) and somehow call it from a Django view whenever I would be needing it.
How should the communication look like beetwen Twisted and Django in this case?
Use the Twisted wsgi container to run Django. This container simply runs the WSGI application in multiple Twisted-threadpool threads, so you can simply call any Twisted API via
blockingCallFromThread. There’s really not that much to it!