Author neologix
Recipients giampaolo.rodola, josiah.carlson, josiahcarlson, neologix, xdegaye
Date 2012-12-28.16:35:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1oMOd=9=5ojaN0PJRkcnZN6Rqp3m4GnABb=U+KRR12=w@mail.gmail.com>
In-reply-to <1356530416.7.0.450670671215.issue16787@psf.upfronthosting.co.za>
Content
> A couple of years ago I conducted similar tests and it turned out that 64k was the best compromise:
> http://code.google.com/p/pyftpdlib/issues/detail?id=94
> Twisted uses 128k.
> I'd be for using 64k and also change asynchat.async_chat.ac_*_buffer_size in accordance.

That sounds reasonable.

However, the mere fact that such constants are duplicated tends to
make me think that async_chat should actually be a subclass of
asyncore.asyncore_with_send (or move c_*_buffer_size to
asyncore.asyncore). Sane default buffering constants belong more to
asyncore than asynchat, no?
History
Date User Action Args
2012-12-28 16:35:18neologixsetrecipients: + neologix, josiahcarlson, giampaolo.rodola, josiah.carlson, xdegaye
2012-12-28 16:35:18neologixlinkissue16787 messages
2012-12-28 16:35:17neologixcreate