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?
For instance, at some point in time, we're going to do have to do
something about floating point representation. We have the ability to
negotiate these capabilities at run-time.
Even if we can negotiate extensions at the protocol level, we need to be
careful about how we actually use them. The client is likely going to be
using whatever standard JSON client comes with their language/environment
and will not neccessarily have ability to change that to make use of the
QEMU specific extension. We don't want to end up with QEMU having a nice
JSON extension for some core feature, but none of the clients being able
to use it in practice.