Re: [Haskell-cafe] Re: syscall, sigpause and EINTR on Mac OSX

From: Joel Reymont To: "Branimir Maksimovic" CC: haskell-cafe@haskell.org Subject: Re: [Haskell-cafe] Re: syscall, sigpause and EINTR on Mac OSX Date: Mon, 12 Dec 2005 02:28:54 +0000

My client _is_ single-threaded, I do not use bound (OS) threads at all. Does this shed any light on why my OpenSSL stuff is working as well as my signal handler? ;-)

If your app is single threaded you should be ok. But then nothing is executed concurrently? why locking at all then? You wouldn;t have problems with deadlocks and signals if single threaded without locking. Now, I m really puzzled. Greetings, Bane.

On Dec 12, 2005, at 12:21 AM, Branimir Maksimovic wrote:

...

In single threaded client you can handle ^C if you like in signal handler without problem. That can be gui program if you like , but console one should be enough. You can implement eg: status, start, pause, quit and so. For now quit will be just fine, later you can add more commands. Make one listener thread in your program for such connections and that's it.

-- http://wagerlabs.com/

_________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/