[Twisted-Python] threadedselectreactor and twistd
antonykummel at yahoo.com
Mon Sep 12 14:28:34 EDT 2005
Not sure what you mean.
If threadedselectreactor can't integrate with twistd,
then the problem that threadedselectreactor solves is
inherent to twistd, in which case twistd is simply
unsuitable for some uses (i.e. GUI)?
--- Bob Ippolito <bob at redivi.com> wrote:
> On Sep 11, 2005, at 11:06 AM, Antony Kummel wrote:
> > Just wondering how and if to integrate
> > threadedselectreactor into twistd. I'm thinking to
> > it for a GUI application which is also a server
> (and a
> > client), so I think using mktap/twistd makes
> > but there is the matter of threadedselectreactor
> > being supported.
> > What I've been thinking is for
> > to have another method, or it could be combined
> > interleave, that accepts a callable that makes the
> > main loop run. It could also be a special reactor
> > say, wxPython, that accepts a wxApp (and
> > automatically), and calls its MainLoop method
> > reactor.run(). This would make it trivial to use
> > twisted.application. It would simple require the
> > service to let the reactor know about its
> > wxApp/whatever.
> > Any thoughts?
> I don't think that's really going to work without a
> bunch of
> refactoring of twistd and special-cases for each
> environment -- which
> is the problem that threadedselectreactor solves in
> the first place.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
More information about the Twisted-Python