Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-19 Thread Jim Davidson
In a message dated 4/19/2001 12:03:25 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: > From:Peter Harper <[EMAIL PROTECTED]> > Subject: ns_cond, threads and file descriptors. > > I've been trying to find a solution to the following problem... > > I have two message queues in shared memo

Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-18 Thread Peter Harper
On Wednesday 18 April 2001 12:30, you wrote: > > A message that gets received or transmitted will involve a form of > > acknowledgement to be sent/received, and therefore a writer thread would > > also need to read and v.v. > > And do you have to retransmit a packet if you don't get the ACK for it

Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-18 Thread Rob Mayoff
> A message that gets received or transmitted will involve a form of > acknowledgement to be sent/received, and therefore a writer thread would also > need to read and v.v. And do you have to retransmit a packet if you don't get the ACK for it within a set time?

Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-18 Thread Peter Harper
Thanks for that Rob. It does raise a couple of other issues, which I guess wouldn't have been clear from my previous email. A message that gets received or transmitted will involve a form of acknowledgement to be sent/received, and therefore a writer thread would also need to read and v.v. I'm

Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-18 Thread Rob Mayoff
> Can someone give me some pointers/solution please? Use two threads to manage the device. One thread simply reads from the device. Every time it gets a message, it puts it on the I-queue and broadcasts the I-queue Ns_Cond. The other thread simply waits on the O-queue cond. Every time it gets

[AOLSERVER] ns_cond, threads and file descriptors.

2001-04-18 Thread Peter Harper
I've been trying to find a solution to the following problem... I have two message queues in shared memory, one for incoming messages, one for outgoing. I have a thread that gets kicked off for processing the incoming messages as they appear on the queue. This thread waits for a particular event