So it forces me to keep all the fired NSURLConnections, right? Otherwise, I can't tell which is which in my delegate methods.
On Wed, Jun 25, 2008 at 10:57 PM, I. Savant <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 10:17 AM, Ling Wang <[EMAIL PROTECTED]> wrote: >> I can't find a way to identify different NSURLConnection instances in the >> delegate methods, for NSURLConnection does not offer access to the >> NSURLRequest used to initialize it. > > Really? The delegate methods I see for NSURLConnection all start > with - (void)connection:(NSURLConnection *)connection ..... > > Seems like the connection passes a reference to itself as the very > first argument. As to getting the NSURLRequest, why do you need to get > it from the connection? This seems like an overall design problem. See > "Creating a Connection" in this document: > > http://developer.apple.com/documentation/Cocoa/Conceptual/URLLoadingSystem/Tasks/UsingNSURLConnection.html# > > -- > I.S. > _______________________________________________ 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 [EMAIL PROTECTED]