Timo van Zijll Langhout

@Giviruk Thank you very much for picking this up! I'll speak to what makes sense to me, though I have no authority when it comes to Shouldly. I agree with...

A bit of further research shows that for the Amazon SQS Transport, the same could be achieved using [SQS Temporary Queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-temporary-queues.html).

I believe RabbitMQ's [auto-delete](https://www.rabbitmq.com/queues.html) option could be used to achieve the same thing there. The semantics for these settings offered by the various providers align pretty well. They share one...

> Can you share some more details about your use case? @timbussmann Absolutely! I have also discussed it in detail with @dvdstelt, should you wish to talk to him. I...

I appreciate your thoughtful response, @timbussmann. If the team indeed considers the feature too niche and/or hard to uniformly get right, I will close this issue and look into using...

> Outside of hte bad formatting, i find the 'after' much more readable. I'm honestly surprised. Can you help me understand your perspective? I'll share mine as well. Without collection...

@CyrusNajmabadi Cheers, that makes sense. I'm afraid it doesn't scale to longer chains, unfortunately. I should have picked an example that made that more clear. How about something like this:...

In practice, though, as soon as a solution starts accumulating messages, people stop actively considering messages. The relevant ones simply drown between the deliberately ignored ones. Diligently suppressing the undesired...

@CyrusNajmabadi Alright, I understand that there are limits to degree of tuning that can be supported. I think we drifted somewhat from the core issue at an interesting point. The...

We got a little side-tracked with the discussion about the implementation and performance. For the sake of progress, let me summarize the gist of this thread based on the most...