[Twisted-Python] Two main loops
jasper at peak.org
Mon Nov 12 11:58:55 EST 2007
Maarten ter Huurne wrote:
> On Sunday 11 November 2007, Jasper wrote:
>> Jean-Paul Calderone wrote:
>>> Practically speaking, you probably don't need to render more than about
>>> 3000 frames per second. ;)
>> That depends. When I send moderately sized objects over Twisted, this
>> approach causes my frame rate to stop while Twisted is busy, and worse
>> makes my GUI non-interactive. For a game, this is generally
> Why would that happen?
> Twisted never blocks; if it has to wait for something (such as a
> transmission buffer becoming ready to accept more data), it will register a
> callback and the reactor will continue (and call your rendering code).
Maybe I'm misunderstanding what's going on underneath, but Twisted sure
seems to block while I send one large chunk of data.
More information about the Twisted-Python