Oops - did not cc plt-scheme.<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">YC</b> <span dir="ltr"><<a href="mailto:yinso.chen@gmail.com">yinso.chen@gmail.com</a>></span><br>
Date: Tue, Apr 21, 2009 at 12:42 PM<br>Subject: Re: [plt-scheme] dynamic-wind & kill-thread<br>To: Robby Findler <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>><br><br><br><br><div class="gmail_quote">
<div class="im">On Tue, Apr 21, 2009 at 12:09 PM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, it is the case that if you're using non-kill-safe- code (as it<br>
sounds like spqsql is), then you cannot kill those threads.<br>
</blockquote></div><div><br>The threads are initiated and managed from web-server. I don't know how it handles interrupted connections (I generally reproduce the bug via refreshing browser quickly), but these threads appears outside my apps control.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You might be able to build a kill-safe wrapper for that code, however.<br>
That is, put all of the code that queries the database into a single<br>
thread and then communicate with that thread in a kill-safe manner<br>
(much like the way the manager thread manages the queue in our kill<br>
safe paper).<font color="#888888"></font></blockquote></div><div><br>Yeah that's my current plan as a stop gap. Eventually I think the kill-safe code should belong in spgsql package itself. <br></div></div><br>Is Trac still the right place to file bugs? I have bugs filed 5 months ago not being touched.<br>
<br>Thanks,<br><font color="#888888">yc<br><br>
</font></div><br>