Re: NSURLConnection set to cache
Re: NSURLConnection set to cache
- Subject: Re: NSURLConnection set to cache
- From: "Eric E. Dolecki" <email@hidden>
- Date: Mon, 18 May 2009 12:21:25 -0400
Thanks - that's good information.
On Mon, May 18, 2009 at 10:35 AM, Keary Suska <email@hidden>wrote:
> On May 17, 2009, at 9:07 PM, Eric E. Dolecki wrote:
>
> I just want to be sure of something - if I set the images to cache, when I
>> load the same url again, the image is coming from memory - because I put
>> in
>> a progress bar and the images loaded already I thought would have an
>> instantly populated progress bar, but they still load with progress
>> (albeit
>> quicker).
>>
>
> If you are using the default cache policy, there is no guarantee whether
> the resource is in memory, on disk, or will be reloaded from its remote
> source (although you could make a reasonable assumption on the latter).
> Also, the cache is always validated in these cases, so there will always be
> some latency.
>
> Keary Suska
> Esoteritech, Inc.
> "Demystifying technology for your home or business"
>
> _______________________________________________
>
> 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
>
--
http://ericd.net
Interactive design and development
_______________________________________________
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