Re: Reading/Writing sockets concurrently

2004-12-12 Thread ajb
G'day all. Quoting Mårten Dolk <[EMAIL PROTECTED]>: > Btw, you import GHC.IO and not System.IO. What is the diffrence between > those two? Hysterical raisins. The terribly good reason why we used GHC.IO (whatever that was) almost certainly doesn't apply any more. Cheers, Andrew Bromage ___

RE: Reading/Writing sockets concurrently

2004-12-10 Thread Simon Marlow
On 10 December 2004 10:55, Mårten Dolk wrote: > Btw, you import GHC.IO and not System.IO. What is the diffrence > between those two? System.IO is guaranteed to be there in the next release :-) Cheers, Simon ___ Glasgow-haskell-users mailing lis

Re: Reading/Writing sockets concurrently

2004-12-10 Thread MÃ¥rten Dolk
Sorry for replying to my own message. You do seem to have one thread reading to the same handle as another thread is reading. Isn't that a problem? After reading Simon's reply it is clear that that shouln't be a problem. /Mårten ___ Glasgow-haskell-user

Re: Reading/Writing sockets concurrently

2004-12-10 Thread MÃ¥rten Dolk
Hi! Thanks for the reply! [EMAIL PROTECTED] wrote: I'm trying to create a client application that needs to read and write data from a socket. What I want to do is to have one thread reading the socket and another thread writing to the same socket, but I can't get it to work. You could take a l

RE: Reading/Writing sockets concurrently

2004-12-10 Thread Simon Marlow
On 09 December 2004 17:46, Mårten Dolk wrote: > I'm trying to create a client application that needs to read and write > data from a socket. What I want to do is to have one thread reading > the socket and another thread writing to the same socket, but I can't > get it to work. > > I know that th

Re: Reading/Writing sockets concurrently

2004-12-09 Thread ajb
G'day all. Quoting Mårten Dolk <[EMAIL PROTECTED]>: > I'm trying to create a client application that needs to read and write > data from a socket. What I want to do is to have one thread reading the > socket and another thread writing to the same socket, but I can't get it > to work. You could t