I am still trying to find a solution to quickly resolve the web server
502 error using NSURLRequest and NSURLConnection. Right now, even if i
set timeoutinterval to 5 seconds, it takes 30 seconds. But more painful
thing is that during that time, it makes the app unresponsive with the
beach
I don't know the full solution, but for a start, is there a particular
reason you are using a synchronous request? Use the asynchronous API
and the main thread won't be locked.
On 7 Jul 2008, at 16:27, Kanny wrote:
I am still trying to find a solution to quickly resolve the web
server 502
Kanny,
On Jul 7, 2008, at 1:37 PM, [EMAIL PROTECTED] wrote:
I am still trying to find a solution to quickly resolve the web server
502 error using NSURLRequest and NSURLConnection. Right now, even if i
set timeoutinterval to 5 seconds, it takes 30 seconds. But more
painful
thing is that
