Mailman 3 December 2010 - Twisted

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com 12 Dec '10

12 Dec '10

1 0

[Twisted-Python] Mail content filter: How to avoid SMTP client finishing sending message before SMTP server finishes receiving it?
by Jack Bates 12 Dec '10

12 Dec '10

Struggling little bit to write a Postfix content filter [1] with Twisted Mail. The content filter will eventually add a cookie to the "from" address, identifying the address that the message was sent to Here's my attempt so far [2] The problem is that the SMTP client finishes sending the message before the SMTP server finishes receiving it - i.e. Client.sentMail() is called before Message.eomReceived() To fix this, I want SMTPClient.smtpState_data() [3], which uses FileSender [4], to wait for the server to finish receiving the message before proceeding to smtpState_msgSent() Is this possible? The only alternative I can think of is to not start sending the message until after the server finishes receiving it - i.e. start sending the message after Message.eomReceived() is called. But this seems to me like it would have worse performance than sending messages at the same time as they're being received - especially for a message with a large attachment How can I avoid the client finishing sending the message before the server finishes receiving it? [1] http://www.postfix.org/SMTPD_PROXY_README.html [2] https://github.com/jablko/cookie/blob/master/cookie [3] http://twistedmatrix.com/trac/browser/tags/releases/twisted-10.2.0/twisted/… [4] http://twistedmatrix.com/documents/current/api/twisted.protocols.basic.File…

1 0

[Twisted-Python] Modifying the logstring
by Einar S. Idsø 07 Dec '10

07 Dec '10

Hi, I have an application which logs activity on a number of servers by two methods: 1. TCP-based queries (app is client) 2. UDP-based logging (app is server) Each server that is being logged is represented by an instance of a server class. TCP-queries are performed by each instance at set intervals, while the UDP-logs are gathered by a global logging instance which listens to a specific port. Events for a given server can be triggered by both protocols, but are handled by the server instance. In other words: An instance of a server class gathers events by polling the server via TCP /and/ by receiving strings from a UDP logging instance which passes received datagrams as strings to the correct instance. Whenever a loggable event results from the TCP queries, the name of the protocol class, which is a subclass of twisted.internet.protocol.Protocol), is used as the logstring. That is fine, as it allows me to distinguish between different server classes, although I cannot distinguish between individual servers. However, when a loggable event occurs on the UDP logging instance, it writes out a longish protocol name which is the same for all the different server classes that are subscribing to events on that UDP port. I have managed to modify the string by doing the following: self.udpLogger = reactor.listenUDP(myPort, UDPListener()) self.udpLogger.logstr = "UDPLogger" Yet when the logged string is passed, as a string, to a server instance for processing, the logstring for any result remains "UDPLogger" no matter how I pass it or what I do to it. I suppose it is expected behaviour that the protocol should "follow" a result, no matter how it is processed down the line, but is there any way in which I can alter the logstring so that instead of "UDPLogger" or the name of the protocol class, it instead uses the server id or any other value that I specify? What I am getting in my logs is: 2010-11-30 10:23:09+0100 [CSS,client] Something happened on TCP 2010-11-30 10:23:09+0100 [UDPLogger] Something happened on UDP What I would like is: 2010-11-30 10:23:09+0100 [CSS (TCP),12345] Something happened on TCP 2010-11-30 10:23:09+0100 [CSS (UDP),12345] Something happened on UDP where 12345 is a unique identifier of the specific server. Or at least: 2010-11-30 10:23:09+0100 [CSS,client] Something happened on TCP 2010-11-30 10:23:09+0100 [CSS] Something happened on UDP so that I know the result from UDP concerns a CSS-server. I hope this was possible to understand. Please let me know if anything needs to be clarified. :) Cheers, Einar

1 2

[Twisted-Python] Porting Apache Mina to Twisted
by Umut Aydin 06 Dec '10

06 Dec '10

Hello everybody. Hope you have a good weekend. I'm trying to port my distributed job server project to twisted but I have a few questions. I just tested twisted with protocol.Protocol socket handler class and it seems like that it creates a new instance for each connection. I want to put those connection's ip addresses into an array. Where should I do that exactly? How can I get ip address and port information out of self.transport.getPeer()? That's all for now. Thank you. -- Best Regards, Umut AYDIN Skype: umut-aydin Blog: http://umut.mobi

4 7

[Twisted-Python] can I detect a child stopped?
by Neal Becker 05 Dec '10

05 Dec '10

Using processProtocol. If a child is stopped (e.g., by SIGSTOP), is there some way to detect this?

2 3

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com 05 Dec '10

05 Dec '10

1 0

Re: [Twisted-Python] - SPAM!!!!!
by vitaly＠synapticvision.com 03 Dec '10

03 Dec '10

twisted-python(a)twistedmatrix.com ADMINISTRATOR!!!! BLOCK THIS RUSSIAN WHO IS SPAMMING OUT LIST PLEASE: Vovan <sasmekoll(a)gmail.com> regards, subscriber. Quoting Vovan <sasmekoll(a)gmail.com>: > ?????? ???????? ??????? ????? ???????? ?? ?????, ????? ??? ???????? > ???????? ?? ?? ?????????? ???????????? ??????? ?? ???????????? > ????????? ???????? ????????? ?? ? ???????? ???????? ????????? ???? > ????????????????? ? ?????????? ???????? ??? ??????. > http://samec.org.ua/?p=202 > ?? ??????? ??????????, ??? ??????????. ????? ??? ??????? ??????? ???????. >

2 1

[Twisted-Python] Handling of NMEA messages
by Albert Brandl 01 Dec '10

01 Dec '10

Hi! We are working on a project that has to extract weather information from an NMEA stream. There is a NMEAReceiver class, but it only extracts GPS information - as expected, since the class is defined in t.p.gps.nmea. We intend to add the NMEA-0183 messages necessary for my purposes. The question is: should we just extend the NMEAReceiver? Weather information is not exactly what one would expect in a class below t.p.gps... On the other hand, it would be strange to create a different kind of NMEAReceiver which knows how to handle the messages dealing with weather data. Best regards, Albert -- Albert Brandl Weiermayer Solutions GmbH | Abteistraße 12, A-4813 Altmünster phone: +43 (0) 720 70 30 14 | fax: +43 (0) 7612 20 3 56 web: http://www.weiermayer.com

4 4