Re: NSURLDownload and resuming a download
Re: NSURLDownload and resuming a download
- Subject: Re: NSURLDownload and resuming a download
- From: email@hidden
- Date: Thu, 12 Jun 2008 11:34:37 -0700
On Thursday, June 12, 2008, at 03:14PM, "Jens Alfke" <email@hidden> wrote:
>
>I think the problem is that RapidShare's response doesn't include an
>ETag or Last-Modified header. Without those, the client can't do a
>conditional GET. And trying to resume a download without using a
>conditional GET is dangerous, because you can't tell if the resource
>you're downloading now is the same version as the one you partially
>downloaded before; so you might end up with a chimera.
>
>I looked through the HTTP 1.1 RFC and didn't see anything about a
>requirement that a server MUST send an ETag if it sends an Accept-
>Ranges:; but I think that's because there are other valid uses of byte-
>range GETs than resuming downloads, and the ETag might not be needed
>for those.
>
Jens,
Thanks for the info... it's very helpful. I presume that Apple has taken the safe route by not allowing the resumption of downloads in that scenario. I guess this means that I'll have to forego NSURLDownload to something a little more "low-level" if I want to be able to support download resumption with Rapidshare.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden