Analogue of Queue.Peek() for BlockingCollection when listening to consuming IEnumerable<T>
问题 I'm using Pipelines pattern implementation to decouple messages consumer from a producer to avoid slow-consumer issue. In case of any exception on a message processing stage [1] it will be lost and not dispatched to an other service/layer [2] . How can I handle such issue in [3] so message will not be lost and what is important! order of messages will not be mixed up so upper service/layer will get messages in the order they came in. I have an idea which involves an other intermediate Queue