Sean Feldman
Sean Feldman
@minascasiou, a [potential workaround](https://github.com/paolosalvatori/ServiceBusExplorer/pull/740) w/o downgrading the SDK is coming.
This is what I've done to verify the customization ``` [Theory] [InlineData(MessageIntent.Publish)] [InlineData(MessageIntent.Send)] [InlineData(MessageIntent.Reply)] async Task Preserve_original_message_intent(MessageIntent messageIntent) { var context = new TestableMessageHandlerContext(); context.MessageHeaders[Headers.MessageIntent] = messageIntent.ToString(); var handler =...
> More to the point, are you trying to test the effect of the Action or make sure the framework actually calls it? I trust NSB will execute it. That's...
The issue is getting access to that callback. Exposing something in the transport package is not such a bad thing. It's not uncommon to mark `private`s as `internal` to have...
A Hello World would be right 🙂
Pausing receiving is a missing feature. This would help in the scenarios described [here](https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/881#issuecomment-1735112192). The ability to dial down concurrency on failures with [automatic rate limitting](https://docs.particular.net/nservicebus/recoverability/#automatic-rate-limiting) is not applicable. It...
Throttling by time, by # of messages, or a custom metric that is related to the number of messages but not 1 to 1.
For example, Intercom API allows up to 16 operations per second. But a single message might represent one or more operations against a 3rd party. Therefore, it's not always 16...
On the broker? The broker will give what it can. This is on endpoints. Endpoints pump messages.
That's doesn't sound right, @ramonsmits. How would the broker know what is "too many messages"? The broker will only throttle based on your namespace tier and MUs provisioned in Premium....