1As far as I know, Apple has never said "you can release code based on
2reverse-engineering the iTunes DAAP implementation."  Here's a message
3I sent to the daap-dev list (mail <daap-dev-subscribe@develooper.com>
4to join).
5
6  From: Nathan Torkington <gnat@oreilly.com>
7  To: daap-dev@develooper.com
8  Subject: Apple
9  Date: Wed, 14 May 2003 12:35:48 -0600
10
11  I spoke to my contact at Apple.  As is usual with Apple, there's no
12  clear "yes" or "no" yet.  The big concern for them is that they don't
13  want to promise that the protocol used in iTunes 4 will be the
14  protocol used in iTunes 5--they don't want people to build software
15  around unpublished protocols or APIs and then complain when they
16  change.  They want the freedom to keep improving.
17
18  That said, there's a ton of history of people doing this.  The haxies
19  are a case in point--kernel tweaks using undocumented APIs.  People
20  use 'em, Apple does not feel hamstrung by them, and the developers
21  have to play catch-up if and when Apple changes those APIs.
22
23  The contact said that a week was sufficient time to wait for a
24  response, after which I can conclude that they won't respond to that
25  question.  He's also going to chase down whoever's responsible for
26  DAAP and see whether there's anything that can be communicated.
27
28  If I don't hear anything after a week, go ahead and release the code.
29  Apple doesn't sue.  If they disapprove legally, they'll send a cease
30  and desist letter.  If they disapprove technically, you'll probably
31  get email from a developer :-)
32
33  So, short answer:
34
35    If I haven't heard anything by Saturday, it's tacit approval to
36    publish the source code.
37
38  Nat
39