On Fri, Jun 5, 2009 at 2:37 AM, Mike Abdullah <cocoa...@mikeabdullah.net>wrote:
> > On 5 Jun 2009, at 00:10, Ammar Ibrahim wrote: > > On Fri, Jun 5, 2009 at 1:55 AM, Keary Suska <cocoa-...@esoteritech.com >> >wrote: >> >> On Jun 4, 2009, at 2:11 PM, Ammar Ibrahim wrote: >>> >>> Hello, I'm about to bang my head against the wall. Here's the situation, >>> >>>> I'm >>>> trying to send many requests using the same request object, I have a >>>> method >>>> which I call frequently, which has the following piece of code: >>>> >>>> >>> This is not all the relevant code, and is insufficient to help. All I can >>> say is, are you re-using the same NSURLConnection, just changing the >>> request? If so, that wouldn't work. NSURLConnection copies the request on >>> initialization. >>> >> >> >> Yes, I'm reusing the same NSURLConnection and just changing the request, >> and >> I can see a lot of weirdness and messed up calls. What's the right way to >> do >> it? And I have my connection object as a class variable. Do I need to >> retain >> it? >> > > Changing the request will make no difference to the existing connection. As > the docs state, the request used to create the connection is copied so it > cannot be further modified. You should create 1 NSURLConnection per > operation. > > Excuse me for the silly question. But I'm going to be doing hundreds of requests, and I have GC ON, how do I create these connections and retain them? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
