<html><body>On 10 Apr, 11:15 am, andrewfr_ice@yahoo.com wrote:<br /><br />>I have been using Twisted with Stackless. I am<br />>interested in writing a more Stackless "friendly"<br />>reactor. I believe a stackless friendly reactor would<br />>call stackless.schedule() whenever possible.<br /><br />I disagree.  Separate reactor implementations are for different OS multiplexing mechanisms.  stackless.schedule() should *not* be called "whenever possible", but rather, whenever stackless tasks have something to do.<br /><br />>I notice there are different types of reactor. I have<br />>been looking at SelectReactor and its base case,<br />>Posixbase. It seems easy enough to modify MainLoop to<br />>put in a stackless.schedule(). However this approach<br />>does not seem to be the most maintainable or<br />>effective, since I would be overriding MainLoop only<br />>to put in one line. What is the proper Twisted<br />>approach to doing this?<br /><br />Don't implement a reactor :).<br /><br />I recently replied to a very similar question in a different thread:<br /><br />    http://article.gmane.org/gmane.comp.python.twisted/13946<br /><br />What about my answer there was not clear?<br /></body></html>