Sounds reasonable, also easy to do.

I suggest the timestamp, if present, should record when the message was last shovelled, and include some indication of the shovel that put this there.

Should this feature be an optional feature of the shovel (default no timestamp)? I was under the impression that the general assumption was that shovels don't modify the messages they 'shovel' about.

Hello.

From the use case i have i think it would be reasonable to make it optional, but i am fine with both options.

Thank you for taking this into consideration.

Should it be separate header, or maybe it's better be included in x-shovelled, since it's already a list of parameters there?

including into the existing is fine but will be slightly
more involved to implement in a backwards compatible way. I trust your judgement:)

On 7 ene 2016, at 14:10, Daniil Fedotov notifications@github.com wrote:

Should it be separate header, or maybe it's better be included in x-shovelled, since it's already a list of parameters there?

—
Reply to this email directly or view it on GitHub.

New header will be easier to configure (and to implement).