Just a quick thought (and before I've had my coffee no less!), but I
think what I'd do is replace the boolean *end-search* with a
*search-state* var that could be either :idle, :running or :stopping.
Then in search-stops, just set *search-state* to :stopping -- you
don't need to actually wait for
On Sep 6, 5:48 pm, K. kotot...@gmail.com wrote:
Hello,
I've got a concurrency problem and it's not really clear to me how to
solve it. I have a Swing GUI doing a search in background with agents
and the results are displayed one after the other, also in background.
Here is, largely
Hi,
Several questions / thoughts:
2010/9/6 K. kotot...@gmail.com:
Hello,
I've got a concurrency problem and it's not really clear to me how to
solve it. I have a Swing GUI doing a search in background with agents
and the results are displayed one after the other, also in background.
Here
Hello,
I've got a concurrency problem and it's not really clear to me how to
solve it. I have a Swing GUI doing a search in background with agents
and the results are displayed one after the other, also in background.
Here is, largely simplified, how I do it:
(defvar- *end-search* (atom false))
