Mailman 3 February 2006 - Twisted

[Twisted-Python] Twisted Python 0.7.0 Prerelease Testing
by Glyph Lefkowitz Aug. 5, 2021

Aug. 5, 2021

hi there, folks: I'd really like to release 0.7.0 but I would like it to be at least a little bit tested before I do so. Could those of you with CVS trees check everything out and see if it performs as advertised? Deeper bugs than that will have to wait for the next release, but I'd at least like to know if it works for someone other than me. Thanks. ______ __ __ _____ _ _ | ____ | \_/ |_____] |_____| |… [View More]

4 5

[Twisted-Python] Get IP of connecting client in XMLRPC server
by Remy C. Cool April 28, 2013

April 28, 2013

Hello, On 18 May 2004, the following message was posted to this mailinglist: Jp Calderone exarkun at divmod.com wrote: >Daniel Newton wrote: > > I have a simple XML-PRC server similar to the example below: > > from twisted.web import xmlrpc, server > > class Example(xmlrpc.XMLRPC): > """An example object to be published.""" > > def xmlrpc_add(self, a, b): > """Return sum of arguments.""" > return a + b def … [View More]

3 3

[Twisted-Python] Problem: spawnProcess() never ending when installSignalHandlers=False
by Matt Feifarek Feb. 3, 2007

Feb. 3, 2007

Hello. I'm using Twisted 1.3.0 on python2.4 on an Ubuntu-Hoary x86 Linux box. I'm using twisted and spawnProcess() with a Queue structure to chain processes that need to be called (specifically, imagemagick commands). I use the "processEnded" event/method of t.i.p.ProcessProtocol to go from one task to the next. Twisted shares a python process with a multi-threaded web-app-kit (Webware) so it has to be run in a thread. This worked well on other older versions of twisted and older versions of … [View More]

6 14

[Twisted-Python] Service dependencies
by Matt Goodall July 10, 2006

July 10, 2006

Hi, I have a couple of services. The second is dependent on the first being fully initialised before the second gets set up. I thought that the order of Service startup was typically handled by organising services in a hierarchy, and that the startup of the hierarchy understood deferreds. I was wrong - service.Application is a MultiService and only understands deferreds in stopService. There's a DependentMultiService class in twisted.internet.app but that entire module has been deprecated. … [View More]

5 4

[Twisted-Python] Status of wxPython support in Twisted 2.1: use wxreactor
by Itamar Shtull-Trauring July 1, 2006

July 1, 2006

wxreactor in Twisted 2.1 uses threadedselectreactor. This means that wx apps ought to use wxreactor, not TSR directly; there are some issues with vanilla TSR wx integration that are also present in wxreactor, but will be fixed in future versions of wxreactor. What's broken (there may be more): 1. reactor shutdown events aren't handled correctly (e.g. Deferred returned from during-shutdown event). 2. Signal handling for e.g. Ctrl-C is caught by wx, not twisted. In order to get these fixed I … [View More]

3 7

[Twisted-Python] Missing feature in detecting stalled PB connections?
by Luc Stepniewski March 7, 2006

March 7, 2006

While using pb.PBClientFactory() with reactor.connectTCP(), I noticed that the specified timeout parameter is only for testing if there is no connection, not if the remote PB replies correctly. I noticed this when one of my remote PB instance was stuck. It was accepting requests, but did not answer anything at all. So the connection is established, and stays indefinitely! You can verify this by yourself by just putting netcat ("nc -vv -l -p 9999" for example) instead of a PB instance. The … [View More]

3 5

[Twisted-Python] Twisted & SOAP
by Richard Townsend March 1, 2006

March 1, 2006

I've been experimenting with the Twisted web/soap.py integration with SOAPpy which appears to do the sort of I stuff I need at the moment. However, a recent message on the Pywebsvcs-talk mailing list said: "Any objection to our diabolical plan to integrate wstools into ZSI and shove SOAPpy to a second class status? We'd like to converge on a single python web services solution, but we're working hard to make sure SOAPpy users can do in ZSI what they can do in SOAPpy..." What effect will … [View More]

3 2

[Twisted-Python] Sending commands when using Telnet client
by Don Smith Feb. 28, 2006

Feb. 28, 2006

Yes, I'm sort of a Twisted newbie, so maybe this has an obvious answer, but I'm just not seeing it. I have a Twisted program that I need to add in the ability to make a client telnet connection to a remote server and send some commands to it and deal with the data received. In my main program I have this line of code: reactor.connectTCP("mytelnethost", 24, Connections.TelnetConnection("myname of object",events,"command to run")) My Connections.TelnetConnection class looks like this: … [View More]

3 5

[Twisted-Python] Re: [Twisted-commits] r16103 - Make loopbackTCP and loopbackUNIX return Deferreds
by Jean-Paul Calderone Feb. 28, 2006

Feb. 28, 2006

On Tue, 28 Feb 2006 05:37:54 -0700, Jonathan Lange <jml(a)wolfwood.twistedmatrix.com> wrote: >Author: jml >Date: Tue Feb 28 05:37:52 2006 >New Revision: 16103 > >Modified: > branches/deprecated-trial-1509/twisted/mail/test/test_imap.py > branches/deprecated-trial-1509/twisted/mail/test/test_pop3.py > branches/deprecated-trial-1509/twisted/mail/test/test_pop3client.py > branches/deprecated-trial-1509/twisted/mail/test/test_smtp.py > branches/… [View More]

2 2

[Twisted-Python] twisted TCP frame size
by Thys Meintjes Feb. 27, 2006

Feb. 27, 2006

Hi, I've recently written a threaded client server application using a custom message protocol. Each message is 49 bytes long and needs to arrive at the client as soon as possible. In the current app I send() each message as soon as all 49 bytes are available, I also recv(49) bytes at the client side (buffering as necessary). The threaded application thus always reads 49 bytes from the network buffers as soon as it is possible to do so. This application consumes about 9% cpu time at full … [View More]throttle. Because I already use the twisted.enterprise adbapi on the client side I decided to get rid of all the client threads and use twisted for the TCP stuff as well. I've written a small test script to determine basic loads and performance: ----------------- #! /usr/bin/env python import psyco psyco.full() import array import sys from twisted.internet.protocol import Protocol,ReconnectingClientFactory from twisted.internet import reactor f = open("wakka", "w") class TRAUReceiver(Protocol): def dataReceived(self, data): print len(data) f.write(data) # f.flush() def connectionMade(self): """ * connection were made, send signon""" print "Signing on...", signon = array.array('B', [ord('T'), 1 ,255, 1, 255]) self.transport.write(signon.tostring()) print "Done" class TRAUClientFactory(ReconnectingClientFactory): def startedConnecting(self, connector): print 'Started to connect.' def buildProtocol(self, addr): print 'Connected.' print 'Resetting reconnection delay' self.resetDelay() return TRAUReceiver() def clientConnectionLost(self, connector, reason): print 'Lost connection. Reason:', reason ReconnectingClientFactory.clientConnectionLost(self, connector, reason) def clientConnectionFailed(self, connector, reason): print 'Connection failed. Reason:', reason ReconnectingClientFactory.clientConnectionFailed(self, connector, reason) reactor.connectTCP('localhost', 55555, TRAUClientFactory()) reactor.run() ------------------ Connecting the above to the server yielded somewhat surprising results: The length of the dataReceived() data between runs varies between 49 and multiples of 49 bytes. I understand this (I think) as the ethernet packet length sweet spot is about 1.3kB and Protocol is propably optimized arround that. This does imply that I need a more elaborate frame caching scheme on the client side than the one I currently have, as another socket connection signals if messages from the current connection must be stored or discarded. Surprisingly, the script data length is reported as continuous 49 bytes at leas 4/10 times it's run, on other runs the print len(data) line looks something like this: 49 12691 49 7938 49 Each second dataReceived() callback is 49 bytes, the rest multiples of 49. When the script reports all frames as 49; cpu consumption is ~33%, when staggered it's ~4%. The dataReceived() call seems overly expensive when compared with the 'raw' synchronous recv(). Paradoxically, padding the 49 byte message with 1000 pad bytes improves the script's performance 8 times; due to the decrease in dataReceived() calls probably. So, 1) is there a way to force dataReceived() to return when a certain data length has been received ? 2) Why is dataReceived() so expensive (if it is) ? 3) Is Protocol the correct tree or are there other ways to handle small time sensitive messages in twisted. Apologies for the longish post. Regards Thys [View Less]

3 2