Z
Zane Thomas [.NET/C# MVP]
BlockingQueue implements a single-writer single-reader queue, something I find
myself needing frequently when working with multiple threads and internet
protocols.
After an instance of BlockingQueue is created the reader can invoke Dequeue and
will be blocked until either there is some object in the queue, or until
BlockingQueue.EOF is true. Setting EOF will eventually result in a null being
returned from Dequeue, but only after all items Enqueued have been retrieved
Source in the Free Things & Other Stuff folder at www.abderaware.com
--
What the caterpillar calls the end,
the rest of the world calls a butterfly.
~ Lao-tzu
Components For Thinkers
www.abderaware.com
zane @at@ abderaware .dot. com
myself needing frequently when working with multiple threads and internet
protocols.
After an instance of BlockingQueue is created the reader can invoke Dequeue and
will be blocked until either there is some object in the queue, or until
BlockingQueue.EOF is true. Setting EOF will eventually result in a null being
returned from Dequeue, but only after all items Enqueued have been retrieved
Source in the Free Things & Other Stuff folder at www.abderaware.com
--
What the caterpillar calls the end,
the rest of the world calls a butterfly.
~ Lao-tzu
Components For Thinkers
www.abderaware.com
zane @at@ abderaware .dot. com