Its really simple, basically, think of it like this : anything you allocate will be automatically released, so [[UIView alloc] init]; will be picked up my the run loops etc and released accordingly. When you stick retain on it, it puts the retain count up by one, starts with 0, then you +1 to it, so now when the auto release pools run, it will ignore your object and wont get released. Likewise, if you run release on it, it will get rid of it from memory. If you dont retain objects when you need to, then problems occur when your trying to call the object, but it has already been released from memory, thus causing epic fail.

If that helps what so ever…and remember to follow @caffeinatedapp for my latest news on my app ;)

Peace

An NSURLConnection has delegate methods ( methods that are called when events happen, just like AS3′s EventDispatcher ), basically the NSURLConnection will stream the required NSURL contents via NSData through that function. Because they are received in parts we have to construct the overall data object, so as you can see, I have set up a NSMutableData object which im appending the NSData that is received. Its pretty simple.

Also im a AS3 developer ;), its a bit like the ProgressEvent in AS3, apart from instead of a percent and bytes loaded / bytes total, it also gives you the data it recieves =].

Hope that helps.

I am trying to create a batch poster in cocoa. I will need to feed in an encoded cookie string and POST it to the server every 500 milliseconds.

Any thoughts?

Also, how does this work:
- (void)connection:(NSURLConnection *)connection
didReceiveData:(NSData *)data
{

I am coming from an AS background, what is this technique called?

Thanks!