Devoloping socket applications with IDLE

[Greg Copeland]

If you're going to insist on using signals with threads, you should
have a single thread catch all signals.  The catching thread should
then notify all other threads of the signal arrival.

Queues and various types of semaphore work wonders for these types of
things...depending on your application needs.


the bean machine <nobody at nowhere.com> writes:
> Hello,
> 	Anyone have any suggestions on how to develop socket apps when
> using the IDLE? I find an annoying problem when I am working on socket
> apps that I can't break out of them. Well it is more complicated, I
> have multipled threads running, and I can't figure out how to trap a
> signal (ctrl-c) and exit both threads. I also get a problem that if I
> try to communicate between two sockets and something goes wrong in the
> flow, the socket will hang blocking waiting for input. It is kind of
> annoying problem and I have to hangup the IDLE environment and restart
> it complete (kill id).
> 
> 
> Are there better ways to make socket programs that are responsive and
> you can break from the keyboard?
> 
> 

-- 
Greg Copeland, Principal Consultant
Copeland Computer Consulting
--------------------------------------------------
PGP/GPG Key at http://www.keyserver.net
5A66 1470 38F5 5E1B CABD  19AF E25A F56E 96DC 2FA9
--------------------------------------------------