Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 0.9.4, 0.9.5, 1.0.0, 1.1
-
Fix Version/s: 1.2
-
Component/s: None
-
Labels:None
Description
For some use cases it would be beneficial to allow parsing of non-standard Json content, where Object field/key names are not quoted (are not surrounded by double
quotes). White space or colon then indicate where the key ends.
Benefits include interoperability (some systems assume that keys need not be quoted, since javascript does not require this) and slightly less verbose content.
Benefit:
1. 5% - 35% space saving
2. Might improve parse speed
Example 1
99 byte, {"name":"John","age":30,"status":2,"email":"john_marcus@gmail.com","hobbies":"football,basketball"}
90 byte, {name:"John",age:30,status:2,email:"john_marcus@gmail.com",hobbies:"football,basketball"}
Example 2
51 byte, {"Mo":1,"Tu":2,"We":3,"Th":4,"Fr":5,"Sa":6,"Su":7}
37 byte, {Mo:1,Tu:2,We:3,Th:4,Fr:5,Sa:6,Su:7}
I don't have immediate plans working on this, but I realized that there might not be drastic performance problems. This because parsing can branch of immediately when no double-quote is encountered where a Map entry name is expected. This allows for isolation of handling of this case, if it is to be implemented.