I am pretty sure you don’t want to use any synchronous requests, though.
Better make an asynchronous one, and handle delegate method callbacks when they
finish. Otherwise, if network flakes out, it can easily clog up everything for
a minute or so, plus it’s just bad to write network code that works
synchronously. :)
-ev
On Jun 27, 2011, at 00:36, R wrote:
> Any opinions on which approach is better.....
>
>
> NSData *data = [NSURLConnection sendSynchronousRequest:request
>
> returningResponse:&response
>
> error:&error];
>
> OR
>
> connectionInProgress=[[NSURLConnection alloc]initWithRequest:request
>
> delegate:self
>
> startImmediately:YES];
> }
>
>
> - (void)connection:(NSURLConnection *)connection didReceiveData:
> (NSData *)data{
> }
>
> - (void)connection:(NSURLConnection *)connection didFailWithError:
> (NSError *)error{
> }
>
> - (void)connectionDidFinishLoading:(NSURLConnection *)connection{
> }
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
