[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-list
Subject:    Re: asynchronous comunication, wxPython and threads.
From:       Zunbeltz Izaola <zunbeltz () gmail ! com>
Date:       2005-06-22 14:32:57
Message-ID: pan.2005.06.22.14.32.57.335365 () gmail ! com
[Download RAW message or body]

On Wed, 22 Jun 2005 09:28:31 -0400, Peter Hansen wrote:


> Almost certainly it is.  It would be simplest to set up a worker thread 
> once, when the GUI thread begins, and simply send requests to it via a 
> Queue.  It can create the socket, connect to the server, communicate, 
> close it down, and go back to waiting all in one place (so to speak... 
> of course this would be several methods all called from a top-level loop 
> in that thread).  No chance of mis-steps.

I corrected the problem. A bit of the comunication was done in the
GUI thread. 

Thanks again for your help.

Zunbeltz


-- 
http://mail.python.org/mailman/listinfo/python-list
[prev in list] [next in list] [prev in thread] [next in thread]