I will first describe my application in a single sentence. Write a server that can serve TCP/UDP clients on several ports, and let the clients communicate with each other in a predefined protocol, while each can 'talk' to the server in a different protocol/port.
In my case where I picked up Twisted relatively late in the project I need Twisted to plugged into my applocation and not the my application plugged-into Twisted (at least at this stage). Is there a way to by-pass this limitation? At this stage the main problem I see is having transport.write will have data transmitted immediately when called from another thread. _______________________________________________ Twisted-web mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
