[Twisted-Python] Question about "starving" the reactor

Phil Mayers p.mayers at imperial.ac.uk
Mon Jun 20 05:39:22 MDT 2011


On 20/06/11 11:29, Orestis Markou wrote:

> By "server" I mean my application's API, by "client" I mean someone
> else that will go and attach callbacks to deferreds I will return. I
> guess the question is, what is the best way to guard my application
> against callbacks that are doing a lot of work. But probably I'm
> confused by conflating the neglecting read() loop with starving the
> reactor.
>
> It might be there's no way to do guarantee something like that, so it
> might be just that everyone should be careful about this.

I don't think you can stop callers of a function doing silly things with 
the return value.




More information about the Twisted-Python mailing list