On Fri, Sep 21, 2012 at 9:25 PM, Sithembewena Lloyd Dube <zebr...@gmail.com> wrote: > Hi everyone, > > What is the recommended way to configure a Django project to listen for and > respond to requests via the TCPIP protocol?
I'm intrigued why you think there would be a a "recommended" way to do this. Django is a web framework. It exists to service HTTP requests. Outside of the limited capabilities of the development server (which, as the name suggests, shouldn't be used in production) it doesn't implement anything at the TCP/IP level. It uses the WSGI interface (or, optionally, the fCGI interface) to service HTTP requests, and relies on other tools to convert TCP/IP traffic into a WSGI request. The libraries that comprise Django could certainly be used for other purposes -- i.e., as a generic interface to database or input handling. However, I can't give you any real advice beyond "do what the docs already say", and pay some extra attention to what happens during the early stages of the request/response cycle in Django. In short -- you're in uncharted, and mostly undocumented territory. Yes, you may be able to use pieces of Django to active what you want. However, you're going to need to take the lead on this yourself. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
