On Wed, Aug 5, 2009 at 1:11 AM, Aaron Bush <asb.b...@gmail.com> wrote:
> A note on how I handled a similar situation in regards to the timeout > requirements you seem to have: > > I had a similar setup where I was forwarding data from clients to servers > and back and forth, etc. I wanted to timeout the connection after some idle > time and ended up using the TimeoutMixin found in > twisted.protocols.policies. It probably does exactly what you are doing but > via a simple class inheritance and variable set. > > -ab > > On Tue, Aug 4, 2009 at 2:35 PM, Kevin Horn <kevin.h...@gmail.com> wrote: > >> On Tue, Aug 4, 2009 at 10:08 AM, John Aherne <johnahe...@rocs.co.uk>wrote: >> >>> This is a really basic problem we are trying to decide about, >>> >>> >>> One side A receives some input from a tcp port - about 100-200 >>> characters, and forwards it to another port B. We do not need to wait for >>> any response. If we get a response we pick that up through line receiver. We >>> also run a calllater to check if we got a response on linereceiver within >>> the timeframe specified. If not we drop the connection. >>> >>> > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > Aaron Thanks for the reply. I have spent some time trying to find out how we might deal with timeouts and not found anything we can use. I'll take a look at that and see what it does. Regards John Aherne
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
