Hi Daniel, >Sorry for any confusion, but I never said anything about using twisted as > >a WSGI container for purposes of ensuring thread-safety. I was only >responding to your question about "how to wrap Django in twisted", and >running Django inside twisted's WSGI container is one way to do that.
Oh alright - sorry :) >If you can afford to make the change, running twisted as a completely >separate service in another process, and implementing communication >between your Django server and your twisted server via a protocol might >simplify things a bit in terms of coordination. This is exactly the kind of architecture I'm currently spying out :) Thanks for confirming the general correctness of my idea! Fabian _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
