[Twisted-Python] Memory usage in large file transfers

Nikolaos Krontiris nkrontir at hotmail.com
Tue Dec 2 12:04:49 EST 2003

----- Original Message ----- 
From: "Itamar Shtull-Trauring" <itamar at itamarst.org>
To: <twisted-python at twistedmatrix.com>
Sent: Tuesday, December 02, 2003 5:38 PM
Subject: Re: [Twisted-Python] Memory usage in large file transfers

> On Tue, 2 Dec 2003 15:46:07 +0200
> "Nikolaos Krontiris" <nkrontir at hotmail.com> wrote:
> > nk: I had originally thought about using basic.FileSender but a) It
> > has been commented as unstable by the twisted development team and b)I
> > need to send a client ID each time I send a single buffer (security...
> > what can you say...). To make sure that I'm not holding the entire
> > file's contents in
> You don't have to use FileSender as is, you could write a variant of it
> using the underlying producer/consumer APIs, that's the solution. See
> http://itamarst.org/writings/OSCON03/twisted_internet-108.html
nk: Ok, I can give it a try, sounds like a good idea. But, since producers
have transport.write in their cores anyway, why should there be a
performance difference between this solution and the way I'm using it (just
calling transport.write)?
> -- 
> Itamar Shtull-Trauring    http://itamarst.org/
> Available for Python & Twisted consulting
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

More information about the Twisted-Python mailing list