Re: [Twisted-Python] Sending jpeg data over TCP/IP

The correct way I think is to use base64 and just one connection after more research. Good to research. Thanks, Garyc --- On Sun, 2/14/10, gary clark wrote: > From: gary clark > Subject: Re: [Twisted-Python] Sending jpeg data over TCP/IP > To: "Twisted general discussion" > Date: Sunday, Feb

Re: [Twisted-Python] Sending jpeg data over TCP/IP

On Mon, Feb 22, 2010 at 2:03 AM, gary clark wrote: > The correct way I think is to use base64 and just one connection after more > research. Good to research. > > Thanks, > Garyc No, base64ing file contents is a terrible thing to do if you're already writing your own TCP-based protocol. Just len

Re: [Twisted-Python] Try/catching yielded Exceptions and getting proper tracebacks

Hi Paul > "Paul" == Paul Goins writes: You're only printing the exception, not a full traceback, so you don't see much. I tend to write what you're doing as follows: from twisted.python import log @defer.inlineCallbacks def xmlrpc_dosomething(self): d = self._do_somethi

[Twisted-Python] Looking for companies doing Twisted

Hi there, I'm not sure if this is the right place to ask, so sorry for the spam in advance. Anyway: I'm looking for companies which might be interested in developing a booking system for an emerging Germany-based long-distance railway undertaking during this year. This will be a distributed sys

[Twisted-Python] IMAP4 Client extrange behavior

Hello all, I have this imap4 client http://www.pastebin.com/m4e387f1a most of the code is barrowed from a IRC friend, bob_f , it works fine but as soon as more that 1 email arrrives to the inbox, it only prints the first new messages but not the others, I wonder what am I doing wrong Thanks a lot

Re: [Twisted-Python] [ANNOUNCE] Twisted 10.0.0pre1 is now released

On Sun, Feb 21, 2010 at 9:50 PM, Jonathan Lange wrote: > Live from PyCon Atlanta, I'm pleased to herald the approaching > footsteps of the 10.0 release. > > Tarballs for the first Twisted 10.0.0 pre-release are now available at: > > http://people.canonical.com/~jml/Twisted/

[Twisted-Python] twisted.protocol.sip

Hello, I'm trying to extend the class twisted.protocols.sip.MessageParser for create my parser. I had read the documentation and I found this: "Shouldn't be connected to actual transport.". What does it means? I can't use that binding it to a socket? I found also that many other object in twisted.

Re: [Twisted-Python] debugging a memory leak

Werner I am using your code, and it shows essentially the same thing as Heapy: the counts of all common objects more or less agree. The 'Total size' shown in Heapy When I start the process, both python object sizes and their counts rise proportionally to the numbers of reconnected clients, and th

Re: [Twisted-Python] debugging a memory leak

On Tuesday 23 February 2010, Alec Matusis wrote: > When I start the process, both python object sizes and their counts rise > proportionally to the numbers of reconnected clients, and then they > stabilize after all clients have reconnected. > At that moment, the "external" RSS process size is abo

Re: [Twisted-Python] Try/catching yielded Exceptions and getting proper tracebacks

Hi Terry, > You're only printing the exception, not a full traceback, so you don't see > much. I tend to write what you're doing as follows: [...] Excellent. I'll give it a try. I had a feeling it was something like that which I was missing. I already understood that inlineCallbacks returns De

Re: [Twisted-Python] debugging a memory leak

Hi Maarten, Your link http://effbot.org/pyfaq/why-doesnt-python-release-the-memory-when-i-delete- a-large-object.htm seems to suggest that even though the interpreter does not release memory back to the OS, it can be re-used by the interpreter. If this was our problem, I'd expect the memory to be

Re: [Twisted-Python] debugging a memory leak

Hi Assuming that if memory not released to the OS can be reused by the interpreter because of a suballocation system used in the interpreter should eventually lead to a leveling out of the overall memory usage over time, that's what I observe with our processes (sitting at several 100 MB per p