3 ms·
The "communication interface" would be the server's network link, which it does indeed employ to: a) receive a request for the current version of the RSS feed
by skymt 14y ago
The "communication interface" would be the server's network link, which it does indeed employ to:
a) receive a request for the current version of the RSS feed ("compilation file")
b) transfer the RSS feed to the client
c) receive and respond to a request from the client for audio files linked to from the RSS feed
This appears to be a correct description of a web server hosting a podcast. I'm also not a lawyer, but I do see a possible loophole in that the claim describes a single machine serving both the feed and the audio files. If the audio is hosted on a separate server or a CDN, it wouldn't violate my reading of the claim. (If that's what you meant, then I guess we agree.) Of course, that's the kind of detail that would need to be hashed out in court before I'd trust it.
- diminoten 14y agoI don't believe that's what they're referencing, as a network link doesn't technically do any of the things you just said. It merely passes on requests for those things. At no time does a network link itself make those requests. Comcast doesn't get sued by the RIAA for delivering packets which contain pirated music, for example.