> sorry, my question wasn't clear: > > I do already disable Nagle by setting TCP NoDelay. > > And I do a reactor.select(0), which sometimes breaks I guess > because of reactor reentry not expected, and it will break > when the reactor is not select() based I guess. > > So the question is: is there an alternative to reactor.select(0) > after a transport.write() to make the reactor call write() on > the underlying socket for all stuff buffered within Twisted?
You should not be calling private reactor methods, it will break things. You can make the max write size (default 128 or 64kb, I forget) bigger by setting some attribute on the transport, but again, the OS will split things up across TCP packets however you want. This is not a very useful thing to attempt - better to instrument firefox to only do certain size reads. _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
