I'm deserializing JSON output from the write_http plugin using ruby-yajl.
yajl was puking on the literal value nan encoded in the output.
[
{
plugin: memcached,
interval: 10,
host: myhost,
values: [
nan,
5
],
time:
Hi Chris,
On Thu, Feb 04, 2010 at 12:52:30AM -0800, Chris Buben wrote:
I'm deserializing JSON output from the write_http plugin using ruby-yajl.
yajl was puking on the literal value nan encoded in the output.
thanks for your patch :) I think it's kind of weird that JSON doesn't
differentiate
Hi Florian,
On Feb 4, 2010, at 1:20 AM, Florian Forster wrote:
thanks for your patch :) I think it's kind of weird that JSON doesn't
differentiate between -inf, inf and nan, but since that's what the
standard says, that's what we should be doing.
My pleasure, and thank you for a great piece
On Thu, Feb 04, 2010 at 02:50:36AM -0800, Chris Buben wrote:
With your proposed approach, won't we still get invalid json on a
platform where isinf doesn't get defined?
In theory, yes.
This doesn't matter in my particular experience (and never will, as on
RHEL we'll always end up with isinf
