On Tue, Apr 20, 2010 at 10:14 AM, Nick Zitzmann n...@chronosnet.com wrote:
On Apr 18, 2010, at 4:36 PM, Hao Lü wrote:
I am doing some analyzing work on a WebView (going through the DOM,
checking
links and texts). Since, sometimes this blocks the GUI, I am
experimenting
using
On Apr 22, 2010, at 12:09 PM, Hao Lü wrote:
Doubt it. I am using a secondary hidden webView dedicated to the background
thread. I was not sure if @synchronized would help, so I added anyway upon
each access. But it did not make a difference. I feel that if it was caused
by things related
On Thu, Apr 22, 2010 at 11:09 AM, Hao Lü ryan@gmail.com wrote:
I did not see such exceptions been thrown, nor any crash
Those are two possible responses the code could have. It could also
just abort the thread, or perhaps act errantly because data it expects
is not the data it has, by
That's true.
- Hao
On Apr 22, 2010, at 11:11 AM, Nick Zitzmann n...@chronosnet.com wrote:
On Apr 22, 2010, at 12:09 PM, Hao Lü wrote:
Doubt it. I am using a secondary hidden webView dedicated to the
background thread. I was not sure if @synchronized would help, so
I added anyway upon each
Hi,
I am doing some analyzing work on a WebView (going through the DOM, checking
links and texts). Since, sometimes this blocks the GUI, I am experimenting
using NSOperation/NSInvocationOperation. What confuses me is that, my
operation stops (not sure if it sleeps or is terminated) upon accessing
On Apr 18, 2010, at 4:36 PM, Hao Lü wrote:
I am doing some analyzing work on a WebView (going through the DOM, checking
links and texts). Since, sometimes this blocks the GUI, I am experimenting
using NSOperation/NSInvocationOperation. What confuses me is that, my
operation stops (not sure
