Assuming both XML plist and JSON are delivered over http, gzipped, which one will be processed faster on an iPhone?
A:
It depends on the data that is delivered and the way it is parsed, but they should both be similar in speed. You should just choose the one that is easier for you to develop a parser and then fine tune the parser.
Conceited Code
2010-08-19 02:24:14
+1
A:
JSON!!!! BASED on ZERO facts. But it is soooooo much easier work with.
John Ballinger
2010-08-19 02:33:23
OI, who down voted me. You can see at the list of comments below that JSON is in fact quicker! And it is easier to work with having down, XML, PLISTS and CSV.
John Ballinger
2010-08-19 03:21:04
A:
In the "Building a Server-Driven User Experience" session of WwDC, an Apple developer stated that PLIST was preferred for being faster and easier to use.
dr
2010-08-19 02:37:57
I think they only concluded that binary pList was faster and easier to use, but there's no way to create binary pList in Java...
Henry
2010-08-19 04:06:34
+1
A:
JSON beats plists according to this: http://samsoff.es/posts/web-services-with-cocoa-surprise
Breton
2010-08-19 02:43:02
+5
A:
A co-worker and I did some rudimentary benchmarks recently to test which was faster for an application we were writing. We tested this JSON framework, and the NSXML parser as well as a TreeNode parser we found in an Objective-C book. Here is the note I sent to the other developers on our team:
The benchmark tested how each library handled getting the filename and path
of 100 assets, 100 times each (for a total count of 10,000 runs per library).
The results are below:
Method Average(s) Total(s)
TreeNode 0.307475 30.747493
NSXML 0.483778 48.377843
JSON 0.233179 23.317870
Mike Trpcic
2010-08-19 02:51:13
Unfortunately no, we did some preliminary research that led us to believe that the NSXML and the JSON imlementations would be fastest, and we had already implemented the TreeNode solution as a first pass. Due to this, we only benchmarked the 3 solutions against one another.
Mike Trpcic
2010-08-19 04:20:04
oh, I thought since plist xml is supported natively, it should have been optimized somehow.
Henry
2010-08-19 17:50:10
That's what we had been led to believe as well, but various online sources steered us away from that. Either way, after using the three solutions above, the JSON parser is lightyears ahead of the others in terms of usability.
Mike Trpcic
2010-08-19 19:34:00
Have you tried TouchJSON? http://code.google.com/p/touchcode/wiki/TouchJSONHowTo
Henry
2010-08-19 21:42:03