If Apple is providing the XML file for third party developer use, but they don't provide any way to monitor changes, does that mean that their intention is for third party apps to regularly refresh from the XML file? Isn't this an extremely expensive operation? Particularly when moving data across a network?

How about interjecting a Core Data app, running on the machine that maintains the XML file? That machine could monitor the XML file with FSEvents and maintain a CD DB that mirrors the XML file, adding new objects or fetching, updating and then saving changes, as appropriate. On the context's WillSaveNotification, it could alert its clients, sending just the updated information.

If this works, the question is, would it be better to maintain mirrored CD DB's on each of the clients (clients will be a mix of Macs and iPhones), and update those databases when changes occur? Or, should they query the server when they need information? The client UI's would be much more responsive if the clients each maintained their own databases, particularly if I wanted to get cover art to the clients, but maintenance gets more complicated.



On Jul 27, 2009, at 10:48 AM, Kyle Sluder wrote:

On Jul 27, 2009, at 10:38 AM, Brad Gibbs <bradgi...@mac.com> wrote:

Are there change notifications for the iTunes database? I'd like to have an iTunes client on a different machine on the local network be notified of changes, rather than having to poll and reload the database regularly.

Nope. No public ones, anyway. You could watch the iTunes DB files with FSEvents or kqueue and refresh over Apple events when you detect a change.

File a Radar, too.

--Kyle Sluder


_______________________________________________

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

Reply via email to