[PEAK] EventDriven, ITwistedReactor, and AdaptiveTask daemons

John Landahl john at landahl.org
Mon Jan 5 23:16:24 EST 2004

On Mon, 05 Jan 2004 21:23:10 -0500, Phillip J. Eby <pje at telecommunity.com> 

> Alternatively, if your application runs from an .ini file, you can add 
> this:
> [Component Factories]
> peak.running.interfaces.IBasicReactor = 
> 'peak.running.scheduler.getTwisted'

That's quite nice.  I've been wondering about how functions or methods 
(rather than classes) might work with [Component Factories]...

> When peak.events lands, I hope to actually make Twisted interopability a 
> bit cleaner.  Right now, a lot of configuration issues arise from the 
> Twisted reactor design assuming a singleton reactor.  When PEAK itself 
> no longer needs a reactor, it won't have to worry about which one is the 
> right one to use any more, because it'll be possible to run as many as 
> you want out of a given "scheduler".

Can't wait.  peak.events sounds like one of the most exciting new 
developments in Python...

More information about the PEAK mailing list