On Jul 26, 2009, at 6:50 PM, slasktrattena...@gmail.com wrote:
On Sun, Jul 26, 2009 at 8:04 PM, Aaron Burghardt<aaron.burgha...@gmail.com> wrote:Interesting and not surprising. What I was suggesting, though, is that the amount of time needed to read the data is probably small compared to thetime spent parsing the data into a plist.Good point. So I ran a second test. Turns out CF is still your best option for sucking in the data. But for the parsing, NSPropertyListSerialization is somewhat faster. So, using a mixed up method, you get a slightly better result. The difference is negligible, but still...2009-07-26 23:34:58.381 tst[91885:10b] CF: Read data in 0.017413 seconds 2009-07-26 23:34:59.385 tst[91885:10b] NS: Read data in 0.021142 seconds2009-07-26 23:44:25.146 tst[93798:10b] CF: Parsed data in 0.560710 seconds 2009-07-26 23:44:26.091 tst[93798:10b] NS: Parsed data in 0.505121 seconds
Nice validation of the relative time difference between reading the data and parsing the data.
So, if I may don my professorial hat for a moment, you have substantially reduced the window of time in which you may collide with iTunes, but you haven't eliminated it. You have an implementation that we *think* will be more robust when it does happen, but it hasn't been tested. Can you confirm it? Going back to your original problem, do you care, or are you satisfied that reading the data first is an adequate improvement?
Regards, Aaron
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
