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
