Image blank when using NSURLConnection but not when using dataWithContentsOfURL?

It looks like you started looking at the guide on developer.apple.com/library/mac/#documen... but didn't finish reading it :).

It looks like you started looking at the guide on developer.apple.com/library/mac/#documen... but didn't finish reading it :) You need to implement the methods that will received infomation about the data being received. - (void)connection:(NSURLConnection *)connection didReceiveResponse:(NSURLResponse *)response - (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data Its all described in the link I provided.

No I've implemented all four of the methods necessary for using NSURLConnection, I just posted the snippet with the actual request. If you think it may be a problem in those then I can post those also. – Millec8 Jun 28 at 19:57 Yes please post the full source :) – madsleejensen 8 Jun at 19:57 Ok full class posted.

– Millec8 Jun 28 at 20:04 any ideas? – Millec8 Jun 29 at 14:50.

Yes I have put traces in my callbacks and everything is being called. I'm not sure I need to do the scheduleInRunLoop because I'm using the same code elsewhere for asynchronous connections that is working correctly with just text. It's just the NSData for the image that isn't returning correctly.

– Millec8 Jun 29 at 13:31.

Turns out it was giving me a bad request because there was a invisible carriage return or white space. Trimming it off with: url = url stringByTrimmingCharactersInSet:NSCharacterSet whitespaceAndNewlineCharacterSet; fixed my problems.

According to your code, you didn't schedule the connection to run.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions