<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">'payload' is the term used for this kind of "in-message custom data"<br>
since the early years of EIP tools (before camel was born)<br></blockquote><div><br></div><div>nested payload, inside of message, I am not sure</div><div><br></div></div></div></div></blockquote><div><br></div>Thinking a bit more about it, I don’t like data (it’s to generic everything is data) and I don’t like payload either (because everything is message payload) can’t we use something like ‘customData’ , ‘userData’, `userKeys` or perhaps something that says a little bit more to what this is.<br><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">
<br>
Any strong reason to avoid it?<br></blockquote></div></div></div></blockquote><div><br></div><div>yeah, let’s keep the once that are there because the are consistent with apple</div></div></body></html>