Re: Efficient XML loading [continuation of NSString from mapped NSData thread]
Re: Efficient XML loading [continuation of NSString from mapped NSData thread]
- Subject: Re: Efficient XML loading [continuation of NSString from mapped NSData thread]
- From: Matt Gough <email@hidden>
- Date: Thu, 15 May 2008 10:11:53 +0200
On 15 May 2008, at 00:20, Jens Alfke wrote:
Because it would be orders of magnitude slower. Even the property
list parser can read the iTunes library in a few seconds. Extracting
all that information via AppleEvents would certainly take minutes.
Taking that amount of time, it would be subject to race conditions,
since the library might change while your script is iterating it.
Fair enough. Out of interest, is it the exchange of the AppleEvents
that is slow, or iTunes handling of them (if you can tell). I remember
long ago writing some plain AppleScripts for an early iTunes and it
could get fairly simple info in 'a few seconds' for large(at the time)
libraries (10,000 songs). Maybe if things have gotten slower since
then someone should report a bug. (No, I don't still have the scripts
handy)
Matt
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden