... Yes. ... Ok. But in this case, would JSON specification itself help a lot? I understand that this is problematic, in that different platforms can choose...
1600
John Cowan
johnwcowan
Feb 26, 2011 8:09 pm
... So you are now conceding that it's invalid JSON to send through unpaired surrogate code units, since they don't correspond to code points? We discussed...
1599
John Cowan
johnwcowan
Feb 26, 2011 8:08 pm
... You are over-interpreting the standard. Of course applications can delete characters: sed -s 's/t//' deletes all t's from the input. And that's all...
1598
John Cowan
johnwcowan
Feb 26, 2011 8:05 pm
... Normalization is non-trivial, and I doubt if any existing Unicode library imposes it on all strings at creation/modification time. Certainly ICU does not;...
1597
Douglas Crockford
douglascrock...
Feb 26, 2011 6:04 pm
... That's not quite right. JSON says nothing at all about number representations. All it knows is sequences of digits with the occasional decimal points. JSON...
1596
John Cowan
johnwcowan
Feb 26, 2011 5:04 pm
... I agree in part. JSON parsers MUST NOT normalize their inputs, for the reasons given upthread. But JSON generators SHOULD generate normalization form C,...
1595
John Cowan
johnwcowan
Feb 26, 2011 4:54 pm
... I think that limit is implied by the statement in the "Security considerations"; section that says that JSON is a subset of JavaScript, where numbers are...
1594
Mark Slater
markosslater
Feb 26, 2011 11:05 am
Regarding the handling of numbers, the RFC doesn't appear to make any mention of native representations of numbers - in fact, it only specifies what...
1593
johne_ganz
Feb 26, 2011 5:08 am
... This is my point. It happens both on the serialization side, but (at least in my opinion), it is much more likely to happen on the deserialization side. ...
1592
johne_ganz
Feb 26, 2011 4:01 am
... True. It would seem, at least to me, that this is one of those nuanced points that either a) Has not been given the proper consideration by Unicode...
1591
Douglas Crockford
douglascrock...
Feb 26, 2011 12:44 am
... I agree....
1590
David Graham
dgraham...
Feb 26, 2011 12:35 am
I had the normalization question while writing json-stream in Ruby as well. I decided the parser shouldn't do Unicode normalization for the following reasons: ...
1589
Tatu Saloranta
cowtowncoder
Feb 25, 2011 11:45 pm
On Fri, Feb 25, 2011 at 3:09 PM, johne_ganz <john.engelhart@...> wrote: ... This is true statement, although the more practical question seems to be what...
1588
Tatu Saloranta
cowtowncoder
Feb 25, 2011 11:25 pm
... Do you have an ACTUAL problem worth discussion, or is this from just purity standpoint? -+ Tatu +-...
1587
johne_ganz
Feb 25, 2011 11:09 pm
... Not according to RFC 4627 it isn't. Section 3, Encoding, "JSON text SHALL be encoded in Unicode.", where SHALL is interpreted via RFC 2119 (i.e., SHALL is...
1586
Douglas Crockford
douglascrock...
Feb 25, 2011 8:00 pm
... For JSON's purpose, Unicode is just a set of code points. It gives some, such as { and }, special meaning. But in strings, everything should simply be...
1585
johne_ganz
Feb 25, 2011 7:44 pm
... Not if it's Unicode. It is a common misconception that "Unicode" is just a set of code points, like say ASCII or EBCDIC. It is not. With ASCII, you can...
1584
Douglas Crockford
douglascrock...
Feb 24, 2011 2:18 am
When the informational RFC insists on Unicode, it is the sense that the encoding is not EBCDIC nor Big5 nor anything other than Unicode....
1583
Douglas Crockford
douglascrock...
Feb 24, 2011 2:06 am
A receiver can do what it chooses to with the character codes it receives. If it wants to delete them or reject them, that is its business. But a JSON channel...
1582
johne_ganz
Feb 24, 2011 1:22 am
In RFC 4627, Section 3 Encoding, it states: "JSON text SHALL be encoded in Unicode. The default encoding is UTF-8." Unicode is defined as: The Unicode...
1581
mehdigholam@...
mehdigholam...
Feb 20, 2011 9:39 am
Hello all, Follow the link for my .net implementation. http://www.codeproject.com/KB/IP/fastJSON.aspx Cheers...
1580
johne_ganz
Feb 13, 2011 1:05 am
Since this is a group dedicated to JSON, I just thought I'd post a note about yet another Objective-C serializer / deserializer: JSONKit, available at...
1579
Tatu Saloranta
cowtowncoder
Feb 8, 2011 7:20 pm
... That would be very useful! I know it might be bit of work, given differing APIs and all.. but then again, it should be beneficial for authors of other...
1578
Jonathan Wallace
ninja9578
Feb 8, 2011 6:05 pm
Well there is a benchmark included in the source, but it's mostly for my own purposes of comparing upgrade versions against the previous version. I think ill...
1577
Tatu Saloranta
cowtowncoder
Feb 7, 2011 10:09 pm
... I suspect many users would like to see comparisons. Maybe blog about it or such (and include test code), or send a link if already published? I don't doubt...
1576
jonathan wallace
ninja9578
Feb 7, 2011 2:11 pm
If there is a standard JSON benchmark that would be nice. I've only compared it to wxJSON, cJSON, and a few others. "People have always been impressed by the...
1575
Tatu Saloranta
cowtowncoder
Feb 4, 2011 12:03 am
... Yes, one would be very useful. I know there are couple for Java (general purpose ones that can also use JSON; and specific ones), but haven't seen many for...
1574
Gregg Irwin
greggirwin143
Feb 3, 2011 8:00 pm
TS> I have noticed that at least half of all JSON projects claim to be TS> faster than anyone else, so measurements could also clear up the TS> situation and...
1573
David Graham
dgraham...
Feb 3, 2011 7:36 pm
If you'd prefer a really slow JSON parser, check out https://github.com/dgraham/json-stream. It's about 20x slower than the Ruby json gem, but it's quite...
1572
Tatu Saloranta
cowtowncoder
Feb 3, 2011 7:12 pm
Interesting. One thing I noticed from the project page is that there are big claims on performance, but it seems to lack links to actual measurements? I was...
