Re: [pmacct-discussion] [PATCH] Minor AMQP improvements
Hi Will, Thanks for both patches. They both make sense and will go in mainstream code. This second one i've already validated and is already applied to the code. The other one i just need some extra minimal time for QA (count it will be committed tomorrow). https://www.mail-archive.com/pmacct-commits@pmacct.net/msg01406.html Thanks again! Cheers, Paolo On Wed, Apr 01, 2015 at 11:18:43AM +0800, Will Dowling wrote: > Whoopsy, > > I forgot to address the other (more important) bug I encountered: > > * Content type is only specified for messages published when the > amqp_persistent_msg configuration option is specified. This information > should always be applied to describe the payload of the message. > > * Modified the content type declaration to "application/json" in line with > RFC4627. > > The second change may cause issues in clients relying on the content type flag > being output already - so I can understand why this might not be adopted. > > That being said, making the change should improve compatability with tools > that correctly interpret known MIME types. > > This patch is designed to be applied on top of my previous one. > > Cheers :) > > > Will Dowling > > > > > ___ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists ___ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
Re: [pmacct-discussion] [PATCH] Minor AMQP improvements
Hi, On 01-04-15 05:18, Will Dowling wrote: > I forgot to address the other (more important) bug I encountered: > > * Content type is only specified for messages published when the > amqp_persistent_msg configuration option is specified. This information > should always be applied to describe the payload of the message. > > * Modified the content type declaration to "application/json" in line with > RFC4627. > > The second change may cause issues in clients relying on the content type flag > being output already - so I can understand why this might not be adopted. > > That being said, making the change should improve compatability with tools > that correctly interpret known MIME types. > > This patch is designed to be applied on top of my previous one. Looks like I made an error indeed in my original amqp_persistent_msg patch. For my use case, application/json as mime-type should not matter. Kind regards, Nick Douma signature.asc Description: OpenPGP digital signature ___ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
Re: [pmacct-discussion] [PATCH] Minor AMQP improvements
Whoopsy, I forgot to address the other (more important) bug I encountered: * Content type is only specified for messages published when the amqp_persistent_msg configuration option is specified. This information should always be applied to describe the payload of the message. * Modified the content type declaration to "application/json" in line with RFC4627. The second change may cause issues in clients relying on the content type flag being output already - so I can understand why this might not be adopted. That being said, making the change should improve compatability with tools that correctly interpret known MIME types. This patch is designed to be applied on top of my previous one. Cheers :) Will Dowling contentfix.patch Description: Binary data ___ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
