On Tue, Jan 26, 2010 at 06:58:32AM -0600, Anthony Liguori wrote: > On 01/26/2010 06:46 AM, Michael S. Tsirkin wrote: >> Yes, I agree we are comnpliant. >> But I also think we should be strict and reject non-JSON >> input just so that clients do not come to depend on it. >> > > If we can make JSON better while preserving compatibility and adhering > to the spec, why wouldn't we?
Adding '' seems very little gain. The pain point wouild be supporting multiple syntax variants, and inability to use external tools to parse such traffic. > For instance, at some point in time, we're going to do have to do > something about floating point representation. What's the issue? There's '.' and there's 'e' ... And maybe we won't need floating point ever ... > We have the ability to negotiate these capabilities at run-time. > > Regards, > > Anthony Liguori If there's an important capability this might make sense. -- MST
