Thank you for all the feedback, it was quite useful. I'm still quite new to twisted, threads and quite the novice programmer, as my questions indicate; this project has been quite enlightening. As a solution I decided that passing off the compute intensive operations in a proper callback to another (set of) machine(s), which is dedicated to these jobs was a more viable longterm solution than this start-stop madness I initially came up with. However, attempting it initially resulted in a great opportunity for me to learn a bit about threads and processes, so it wasn't necessarily a waste of time.
<br>Thanks again!<br>-joe<br><br><div><span class="gmail_quote">2007/12/17, <a href="mailto:twisted-python-request@twistedmatrix.com">twisted-python-request@twistedmatrix.com</a> <<a href="mailto:twisted-python-request@twistedmatrix.com">
twisted-python-request@twistedmatrix.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send Twisted-Python mailing list submissions to
<br> <a href="mailto:twisted-python@twistedmatrix.com">twisted-python@twistedmatrix.com</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python">
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:twisted-python-request@twistedmatrix.com">twisted-python-request@twistedmatrix.com
</a><br><br>You can reach the person managing the list at<br> <a href="mailto:twisted-python-owner@twistedmatrix.com">twisted-python-owner@twistedmatrix.com</a><br><br>When replying, please edit your Subject line so it is more specific
<br>than "Re: Contents of Twisted-Python digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Re: Twisted-Python Digest, Vol 45, Issue 18 (<a href="mailto:glyph@divmod.com">glyph@divmod.com</a>)<br><br><br>
----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 16 Dec 2007 10:13:08 -0000<br>From: <a href="mailto:glyph@divmod.com">glyph@divmod.com</a><br>Subject: Re: [Twisted-Python] Re: Twisted-Python Digest, Vol 45, Issue
<br> 18<br>To: <a href="mailto:twisted-python@twistedmatrix.com">twisted-python@twistedmatrix.com</a><br>Message-ID:<br> <<a href="mailto:20071216101308.21558.555241615.divmod.xquotient.2970@joule.divmod.com">
20071216101308.21558.555241615.divmod.xquotient.2970@joule.divmod.com</a>><br><br>Content-Type: text/plain; charset="utf-8"; format="flowed"<br><br>On 10:04 am, <a href="mailto:josef.robert.novak@gmail.com">
josef.robert.novak@gmail.com</a> wrote:<br>>Ok I see this will definitely not work as we are talking about threads<br>>and<br>>not processes so os.kill is of no use to me. I guess there is no way<br>>to<br>>track these new threads and stop/pause/restart them based on some other
<br>>decision logic? Would have been nice if there were though... -joe<br><br>If you really think about it (and I mean really think about it, computer<br>science-y stuff, understanding what sharing state in threads really
<br>means, how the Python interpreter happens to work now, considering all<br>the ways it could work) the idea of stopping and restarting threads is<br>inherently broken. You might be able to make it work, by accident, for
<br>a few simple cases, but there would be no reasonable way to guarantee<br>safety except for forcing the explicit use of channels to communicate<br>between threads. If you're doing that, though, you're effectively using
<br>processes. SIGSTOP and friends work just fine on them :).<br><br><br><br>------------------------------<br><br>_______________________________________________<br>Twisted-Python mailing list<br><a href="mailto:Twisted-Python@twistedmatrix.com">
Twisted-Python@twistedmatrix.com</a><br><a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br><br><br>End of Twisted-Python Digest, Vol 45, Issue 20
<br>**********************************************<br></blockquote></div><br>