forcibly terminating io operations

[arnab321]

in the thread, if a connection is made with the http server, it takes too long at this line. how do i implement the "cancel connection" feature found in many j2me apps?

int resc=hcon.getResponseCode();

but calling thread.interrupt() during this wait does not terminate the operation.

i hv a thread like this

class thread extends Thread{
....
public void run(){
http();
}
public void http() throws IOException{
...make hcon a connection
int resc=hcon.getResponseCode();
System.out.println("a");
}
}






and calling it like this:
thread a=new thread();
a.start();
....when reqd., a.interrupt() is called. but it does not print "a".keeps on waiting

[Nicholas Jordan]

The only solution I have found to this problem ( which I have not tried ) is:

class TerminatableConnector extends Thread
{
   // code....
}
main()
{
  TerminatableConnector tc = new TerminatableConnector();
  tc.setDaemon(true);
}

Which places this thread at the mercy of main and other threads. The Thread class has some sort of done() which can be polled in a lower priority thread. I did a great deal of convoluted experimenting on this with my first project and found that this approach brings responsiveness within reason.

[arnab321]

hey, i dont think MIDP 2.0 supports the setDaemon() method, does it?