Dispatch context

Some neat features will become available if we can have knowledge about whether we're operating in the context of a Dispatch operation. For example:
* Propagating the CorrelationId for an operation (implemented)
* A "Bus.Reply" concept for things like reporting progress of long-running orchestrations
* Others I haven't thought of right now... :wink:

Please consider. :smile:
Yes we should. Whoops. :(


On Sat, Jun 28, 2014 at 9:51 PM, Andrew Harcourt <notifications@github.com>
wrote:

> In
> src/Tests/Nimbus.IntegrationTests/Tests/SimpleDispatchContextCorrelationTests/CommandHandlers/FirstCommandHandler.cs:
>
> > @@ -0,0 +1,18 @@
> > +﻿using System.Threading.Tasks;
> > +using Nimbus.Handlers;
> > +using Nimbus.IntegrationTests.Tests.SimpleDispatchContextCorrelationTests.MessageContracts;
> > +
> > +#pragma warning disable 4014
> > +
> > +namespace Nimbus.IntegrationTests.Tests.SimpleDispatchContextCorrelationTests.CommandHandlers
> > +{
> > +    public class FirstCommandHandler : IHandleCommand<FirstCommand>
> > +    {
> > +        internal static IBus Bus;
> > +
> > +        public async Task Handle(FirstCommand busCommand)
> > +        {
> > +            Bus.Send(new SecondCommand());
>
> Should we be awaiting this? Will have a look.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/NimbusAPI/Nimbus/pull/114/files#r14323832>.
>