On Wed, Jan 7, 2009 at 9:43 AM, marc hoffman <[email protected]> wrote: > > wow, that was indeed it. odd, i could have /sworn/ i had seen a separate > class method in the docs with a "shouldStart" parameter, and that this one > was supposed to not start it. teaches me to trust my memory ;P
Well, your memory isn't *that* bad :) There is -initWithRequest:delegate:startImmediately:, but it starts the connection unless you pass NO to startImmediately. The other forms of init for NSURLConnection (including +connectionWithRequest:delegate:) will start immediately. > anyways, all working now, thanks a lot! Great! You may want to consider filing a bug with Apple about your case. Seems like -start should be benign on an already started connection, but they can probably at least clear up the documentation about when one can and/or should call -start. The docs say "Causes the receiver to begin loading data, if it has not already.", but it seems here it caused the data to begin loading a second time, later crashing after the connection was released. Jason _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
