Re: NSURLConnection - data comes in after completion
Re: NSURLConnection - data comes in after completion
- Subject: Re: NSURLConnection - data comes in after completion
- From: Michael Ash <email@hidden>
- Date: Tue, 3 Aug 2010 14:16:28 -0400
On Mon, Aug 2, 2010 at 1:20 PM, Fritz Anderson <email@hidden> wrote:
> On 2 Aug 2010, at 11:50 AM, David Duncan wrote:
>
>> On Aug 2, 2010, at 9:40 AM, Fritz Anderson wrote:
>>
>>> The didReceiveData: callback asserts that the data accumulator exists. In certain circumstances (it seems to be with four of these requests started nearly simultaneously), the assertion is triggered. self.dataAccumulator is nil, and there is a significant amount of data coming in - 30K out of a 200K image.
>>
>>
>> It is unclear how you are managing having multiple requests. Do you have multiple instances of this class, or does -loadAsync just get called 4 times?
>
> Yes, I have multiple instances of this class. Any one loader object has exactly one NSURLConnection in its entire lifetime.
>
> This is a loader for images in a table. Up to four image cells may be visible at a time. When the table first appears, each visible cell creates a loader object, and each of those initiates a download. Four downloads, but a loader doesn't know about anything but its own NSURLConnection.
Just to be sure, have you logged the value of 'connection' in the
delegate callbacks to ensure that it's not a different connection
causing the spurious calls?
Mike
_______________________________________________
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