Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I doubt itmss is anything more than itms over SSL. And I doubt that itms/daap are anything more than HTTP over high numbered ports, with maybe some extra metadata lurking somewhere. It would be too expensive for Apple to invent a completely new protocal when HTTP can be beaten into submission for virtually any task (e.g. SOAP).

    Any clues where they're using itmss vs. itms? Sending purchased tracks perhaps?

    • by pudge (1) on 2003.05.01 12:08 (#19667) Homepage Journal
      I did s/itms/itmss/ and iTunes threw me an error. So something else is going on.

      And yes, itms and daap (and most likely itmss) are just HTTP, but requests to send and what to do with the results, these need to be discovered. I didn't mean to say they weren't HTTP, just that there's another sort of protocol on top of HTTP.
      • Re:itmss (Score:3, Informative)

        Yep. A few people on xml-dev have poked around and determined that itms (at least) is a RESTful protocol. Replacing itms: with http: (and adding a port number perhaps) is sufficient for examining the XML documents that iTunes builds into an interface. At first glance, looks like a the presentation portion is an XMLified nib file of sorts. :-) (The data portion is a plist, of course.)