On Tue, Jan 26, 2010 at 06:47:12AM -0600, Anthony Liguori wrote: > On 01/26/2010 05:43 AM, Luiz Capitulino wrote: >>> The issue I see isn't related to unsigned. Apparently we currently >>> accept values such as 'a' as valid strings. Since this is not valid json >>> we probably should reject it just in case we will want to switch to >>> another json library, otherwise clients might come to depend on >>> non-standard behaviour. >>> >> This extension is only used internally by QEMU and we find it >> very convenient otherwise we would have to escape strings in >> dicts and lists, which is error prone and time consuming. >> > > Actually, I was reading the JSON RFC last night and came across: > > "A JSON parser transforms a JSON text into another representation. A > JSON parser MUST accept all texts that conform to the JSON grammar. > A JSON parser MAY accept non-JSON forms or extensions." > > So we are fully JSON compliant in our current implementation. > > Regards, > > Anthony Liguori
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. -- MST
