Re: [aerogear-dev] message format change proposal

+1 for user-data - Christos On Oct 28, 2014, at 2:30 AM, Daniel Passos <daniel(a)passos.me&gt; wrote: -1 to payload, +1 to user-data || userData -- Passos On Mon, Oct 27, 2014 at 4:36 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > On Mon, Oct 27, 2014 at 5:50 PM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > >> On Mon, Oct 27, 2014 at 03:30:51PM +0100, Erik Jan de Wit wrote: >> > > On Mon, Oct 27, 2014 at 3:15 PM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> > > 'payload' is the term used for this kind of "in-message custom data" >> > > since the early years of EIP tools (before camel was born) >> > > >> > > nested payload, inside of message, I am not sure >> > > >> > >> > 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. >> +1 to userData, clearly communicates intent (if y'all dislike payload) :D >> > > how about user-data ? > (due to consistency ?) :) > > > > >> >> -- >> qmx >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev