Stopped requiring the timeout id to be set by the persister

Related to https://github.com/Particular/NServiceBus/issues/2169
I think we should have a factory for control messages

On Monday, June 9, 2014, Andreas Öhlund <notifications@github.com> wrote:

> In src/NServiceBus.Core/TransportMessage.cs:
>
> > @@ -51,6 +51,18 @@ public TransportMessage(string existingId, Dictionary<string, string> existingHe
> >          }
> >
> >          /// <summary>
> > +        /// Creates a new transport message with the given headers and body
> > +        /// </summary>
> > +        /// <param name="existingHeaders">The existing headers</param>
> > +        /// <param name="body">The body, can be byte[0] for control messages</param>
>
> Yes, that was what I meant. How can we rephrase?
> … <#1467edfb9a005ad4_>
> Sent from my iPhone
>  On 09 Jun 2014, at 06:17, John Simons <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote: In
> src/NServiceBus.Core/TransportMessage.cs: > @@ -51,6 +51,18 @@ public
> TransportMessage(string existingId, Dictionary<string, string> existingHe >
> } > > /// <summary> > + /// Creates a new transport message with the given
> headers and body > + /// </summary> > + /// <param
> name="existingHeaders">The existing headers</param> > + /// <param
> name="body">The body, can be byte[0] for control messages</param> Isn't
> this wrong? I thought the body actually needs to be byte[0] for control
> messages otherwise fails? — Reply to this email directly or view it on
> GitHub.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Particular/NServiceBus/pull/2170/files#r13529193>.
>