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?
Ccna final exam - java, php, javascript, ios, cshap all in one. This is a collaboratively edited question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
Friday, February 10, 2012
killProcess blocked by DefaultHttpClient.execute
Tags
android,
java,
Tips For Programmer
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment