Jeremy D. Miller
Jeremy D. Miller
From a conversation on Twitter w/ @bleroy today. Might lead to a pretty clean syntax.
Inspired by a project at work. What if the system is hosed so badly that no message could possibly be processed? Shut the listener down altogether, find some way to...
For the times when there's message persistence. *Might* decide the cancellation should be on the application and not the parent process?
Don't recover incoming messages for a listener that's currently stopped or the circuit breaker is worthless
Think it's just a validation to not allow that in configuration
There's a unique InMemoryScheduledJobProcessor for each lightweight, local queue + the JasperRuntime. The diagnostics are useless. Might be worth just improving the diagnostics on `IJasperRuntime` to show you everything that's...
*To be clear, this will **not** be any kind of full blown, alternative AspNetCore framework because that way lies madness, heartbreak, and failure* **Goal**: Mechanism to utilize Jasper's execution pipeline...
Basically just skip the silly "look up the message type handler" step within CommandBus. So the signature would be something like just `InvokeAsync(T message, CancellationToken token) : Task`. Maybe pair...