Mike,
I've used the
android.net.http.RequestQueue class for large, high latency calls.
This class takes care of running the request in a seperate thread and
allowing you to create a callback to handle the result.
You can find an example of using the RequestQueue at
http://www.anddev.org/doing_h
You can look in I believe /data/anr/traces.txt to find a dump of the stacks
of all processes and threads when the ANR happened, which should tell you
what your thread was stuck doing at the time.
On Thu, Dec 4, 2008 at 4:27 PM, <[EMAIL PROTECTED]> wrote:
>
> Yes, I've already coded that up and it
Yes, I've already coded that up and it behaves identical to
HttpURLConnection. So that's
not the root cause of this.
I just tested this on 3g vs. my home wireless and it too behaves
identically, so it's not the
kind of net connectivity that's causing this either.
Mike
On Thu, Dec 4, 2008 at 4:2
[EMAIL PROTECTED] wrote:
> So I switch over to using DefaultHttpClient and friends and it...
> behaves the same way.
> (I assume that's what you meant by HTTPComponents aka the apache stuff?)
Yes, the stuff in org.apache.http.*. Documentation can be found at
http://hc.apache.org, and example cod
So I switch over to using DefaultHttpClient and friends and it...
behaves the same way.
(I assume that's what you meant by HTTPComponents aka the apache stuff?)
Does anybody have any direct experience trying to post largish amounts of data?
It doesn't seem like what I'm doing here is particularly
enervatron wrote:
> FWIW, I'm using HttpURLConnection to create and read/write the data,
Have you tried switching to the HTTPComponents API in Android? It's
possible the problem is limited to the implementation of
HttpURLConnection, and your problem will go away by using another HTTP API.
--
On Thu, Dec 4, 2008 at 2:25 PM, Justin (Google Employee) <[EMAIL PROTECTED]>
wrote:
>
> My guess is that you're calling Thread.run() from the UI thread. This
> will execute the thread in the UI thread. You need to call Thread.start
> () for it to execute in its own thread.
No, I'm definitely cal
My guess is that you're calling Thread.run() from the UI thread. This
will execute the thread in the UI thread. You need to call Thread.start
() for it to execute in its own thread.
Let me know if this isn't the issue.
Cheers,
Justin
Android Team @ Google
On Dec 4, 1:33 pm, enervatron <[EMAIL P
8 matches
Mail list logo
