Routemeister in it self is designed to be small and solve one thing well.
How-ever, the powers of it is still great. Lets presume you need a router that
routes messages to one particular instance of an object. This could be useful
for e.g. aggregating something based upon a bunch of events.
Currently Routemeister does not come with built in support for a
request-response scenario, much because I haven't decided on how this should
behave and there hasn't been a need for it yet. But this doesn't stop you from
implementing support for it.
Routemeister is asynchronous, hence it relies on…
Routemeister is not a big library. It's quite tiny actually and after having
felt at it a bit in real usage, I decided to make a few changes to it and I now
consider to API "stable" so it has reached v1.0.0.
What is it?
For new readers... Routemeister is a small NuGet built with one single purpose.…
With the release of v0.3.0 the internal routing as well as the strategy for
creating handlers got access to a MessageEnvelope. The envelope carries the
message and custom state. This custom state can with middlewares be used to e.g.
assign a certain Autofac child lifetime scope