• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Is there a known bug in NSUrl?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is there a known bug in NSUrl?


  • Subject: Re: Is there a known bug in NSUrl?
  • From: Robert Nicholson <email@hidden>
  • Date: Wed, 18 Feb 2009 08:15:44 -0600

In the cases where I see this occur I'd say that the time from start to first resume attempt is less than 30 minutes. I do not believe it could be related to session timeouts. Secondly, in my mind it's a bug if the application simply refuses to continue. Often what you see is if it cannot continue / resume it will start again. I'm not seeing that I'm seeing it literally go no where when it sees that it cannot resume and only if I go out of your way to delete the file will it make any form of progress by starting again.

On Feb 18, 2009, at 2:22 AM, Sherm Pendley wrote:

On Wed, Feb 18, 2009 at 12:00 AM, Robert Nicholson <email@hidden > wrote:
So, I often see this same behavior in Safari, iTunes etc whereby when it's downloading something and you try to resume. It simply will not resume or will say timeout _until_ you remove the file and start again. In iTunes the progress bar simply will not show any more progress until the previous partially downloaded file is removed. I've seen this in Software Update as well where you'll have to go in it's cache to delete partially downloaded updates or it will never resume from where it's left off.


The fact that I see these across so many apps tells me its possibly a framework issue.

Anybody seen this behaviour on their machines?

I've seen it, but I wouldn't be so quick to assume it's a bug in NSURL - resumed downloads requires a cooperative web server that understands and responds appropriately to the HTTP Range: header. Also, with ADC downloads for instance, your session key is part of the URL, so if your session times out what you'll actually be requesting is a different URL, not a resumed download of the same URL.

I'm not saying it *isn't* a bug - just that there are other possible explanations, and I haven't seen any evidence to support one theory or another.

sherm--

--
Cocoa programming in Perl: http://camelbones.sourceforge.net


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Is there a known bug in NSUrl?
      • From: Mike Abdullah <email@hidden>
References: 
 >Is there a known bug in NSUrl? (From: Robert Nicholson <email@hidden>)
 >Re: Is there a known bug in NSUrl? (From: Sherm Pendley <email@hidden>)

  • Prev by Date: Re: Moving oneself to /Applications (or ~/Applications)
  • Next by Date: Re: display unicode string one character at a time, actually quite simple after all
  • Previous by thread: Re: Is there a known bug in NSUrl?
  • Next by thread: Re: Is there a known bug in NSUrl?
  • Index(es):
    • Date
    • Thread