Thank you. Now I'm convinced of it. On Wed, Jun 25, 2008 at 11:20 PM, I. Savant <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 11:02 AM, an0 <[EMAIL PROTECTED]> wrote: >> So it forces me to keep all the fired NSURLConnections, right? >> Otherwise, I can't tell which is which in my delegate methods. > > I believe so, yes. Presumably you'd have a controller that knows how > to, say, -getResourceAtURL: ... this method would create a request, > then create a connection with that request. It would conceivably add > that connection (if it was successfully created) to some collection > that identifies it in whatever way is useful. Perhaps an array of > dictionaries (whose keys are "url" and "connection", with methods to > find "connection for url" or vice-versa)? It depends on what you're > trying to do. > > Depending on the delegates that are 'fired', you can update the > appropriate progress UI, handle the resource and remove the connection > from your collection, etc. > > -- > 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]
