Stijn Moreels
Stijn Moreels
That would be a cool feature, indeed. I see some similarity with #25 and #36 .
Sounds like a plan! 🎉 Thx a lot for documenting/investigating this so thoroughly. Will see if I can work on something while you're gone. 👍
The feature is done being designed and almost picked up for development: https://github.com/Azure/azure-service-bus/issues/454#issuecomment-1645816895 Maybe we can wait a bit for it.
Yes, think that is a good approach. Unless of course this is very critical for other projects, otherwise I would be in favor to wait a bit for Microsoft to...
Ah yes, but I'm wondering what Impact this could have on the performance/scaling/cost of Service Bus as for every message, there will be two in the queue. Otherwise, this is...
> Any update on this? We need this feature at NxtPort to implement a retry mechanism with custom backoff times. We are working on a circuit breaker, but that would...
I think it is possible, though, to defer the message yourself in the message handler, add an application property with a timestamp, and filter with another message handler for certain...
We're talking about the same thing here 😉
Somre more guidance for this issue is proparly required. What is considered a 'temporary failure'? How should it be handled? The message pump has now something of a handling logic,...
OK, cool, after #141 is done, we can maybe create some options a consumer can configure on the message router.