split sla from critical time

Since they can write a new behavior to pull them out of the context them self I'd say we make the change instead of poluting the incoming message with headers?

Possibly we should go through and do the same for other headers that's only used by audit?

Sent from my iPhone

> On 07 Aug 2014, at 23:51, Simon Cropp <notifications@github.com> wrote:
> 
> In src/NServiceBus.Core/Monitoring/ProcessingStatisticsBehavior.cs:
> 
> > @@ -0,0 +1,24 @@
> > +﻿namespace NServiceBus
> > +{
> > +    using System;
> > +    using Pipeline;
> > +    using Pipeline.Contexts;
> > +
> > +    class ProcessingStatisticsBehavior : IBehavior<IncomingContext>
> > +    {
> > +        public void Invoke(IncomingContext context, Action next)
> > +        {
> > +            //since the audit captures the physical message headers then lets place them there
> @andreasohlund possibly. but i dont know what other extensions people have written that may expect those headers to exist.
> 
> —
> Reply to this email directly or view it on GitHub.