Skip to main content

killProcess blocked by DefaultHttpClient.execute



I'm writing an application which at the beginning connects with the server and waits for its response. To achieve this I'm using DefaultHttpClient.execute method with response time set to default. This execution is triggered as a separate thread which is set as daemon. Still, when I try to kill an application through android.os.Process.killProcess call there is a significant lag, which I'm guessing is related with DefaultHttpClient.execute mechanism (not-daemon thread execution?). Is there a way to kill my connection just after killProcess call?




Comments

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?