I always create a separate delegate object for each URLConnection. It
makes the delegate code simpler, and avoids problems like the one
you've run into.
—Jens
smime.p7s
Description: S/MIME cryptographic signature
___
Cocoa-dev mailing list (Cocoa-
Heh, you're right. I went looking through my code and realized that I've
solved it in the past by subclassing NSURLConnection to add a request
accessor or by maintaining a dictionary of connection->request objects in
the delegate.
I'm so used to my subclass that I forgot it's not in real Cocoa
Hi Rob
Thanks for the answer. Unfortunately I do not see the points of
getting the NSURLRequest. For example if I implement the delegate method
- (void)connectionDidFinishLoading:(NSURLConnection *)connection;
there is no NSURLRequest here (and no request accessor on the
NSURLConnection) .
You get the URL out of the NSURLRequest, which you can fetch at various
points.
-Rob
On Mon, Mar 24, 2008 at 2:02 PM, Laurent Cerveau <[EMAIL PROTECTED]> wrote:
> Hi
>
> When using NSURLConnection is there a way to get back the NSURL from
> the NSURLConnection (in a delegate method)? Apparently
Hi
When using NSURLConnection is there a way to get back the NSURL from
the NSURLConnection (in a delegate method)? Apparently if I log the
NSURLConnection it knows what URL is concerned but I do not find an
accessor for it.
Thanks
laurent
___
