I have a worker thread in my application that is responsible for three different things. Requests for two of the jobs turn up in Queues that I have written, the other job is
I discovered, that if you call NetworkStream.Read
with size = 0
, it will actually block:
networkstream.Read(buffer, 0, 0);
The documentation is not clear about this, but for me it worked.
The simplest way is probably to use an additional thread which reads synchronously and puts extra data onto an extra queue.
Alternatively you could use asynchronous IO, but that's somewhat tricky - and you'd still need to have some additional queue.
Although Socket
has a Select()
method (and you can get at a socket from a NetworkStream
) I don't believe it exposes this functionality in a way which lets you mix it with other kinds of wait handles.
You can use the async methods of the NetworkStream and set a ManualResetEvent in the EndReceive method.
// ...
netStream.BeginRead(buffer, offset, callback, state);
// ...
inside the callback method
netStream.EndRead(ar);
netStreamManualResetEvent.Set();
then your code
while (notDone)
{
WaitHandle.WaitAny(new WaitHandle[] { queue1.HasData, queue2.HasData, netStreamManualResetEvent} );
// ...
if (netStream.DataAvailable)
{
// make the buffer from the AsyncState in the callback method available here
// process buffer
}
}