Cldc midp wtk confusion

Question

hi,
this might be a j2me-newbe's stupid question, but i have the following problem:
in cldc 1.1 the method interrupt is defined for the class thread, while in cldc 1.0
it is not. in the javadoc of wtk20 the interrupt method is not available for thread,
in wtk22 it is. in
http://developers.sun.com/techtopics/mobility/getstart/articles/survey/
i can see that both midp1 and midp2 can be on top of cldc1.0 and cldc1.1 as well.
so my QUESTIONS are:
-for example the specification of the nokia 6600 says its a cldc1.0 mobile. is it possible to write some software, that stops threads on such a mobile anyway,
since i can use midlets created using wtk22, which includes the thread.interrupt-method ?
-what exactly does the wtk represent, an implementation of cldc or midp?
thanx
eddi

Answer 1

This is how I usually deal with such things: I display a form on the screen while the network processing is done in the background. In the commandAction() method of my main class I start 2 threads: one which will display the special form and another one which does all the data processing.          public void commandAction(....) {
                  WhileProcessingThread whileProcessing = new WhileProcessingThread(this);
               whileProcessing.start();
            Thread actualProcessing= new Thread(this);
            actualProcessing.start();
           }The first thread (whileProcessing) is handle by a special class (WhileProcessingThread) which takes a Form object and displays the content of the form in the run method:          public void run() {
          while (true) {
               if (!doneProcessing) {
                               //display something on the screen
          } Also on this form, I have a 'back' command which returns the application to the previous screen, so that if the data processing takes forever, then we can return from that screen.
The thread which does all the data processing (actualProcessing) is handled in the main class which in my case implements the Runnable interface; in the run() method, after all the processing is done, I simply set the variable doneProcessing to true and join on the thread so that I assure that the thread which displayes the form will end.
Again, if the application hangs forever, I have the back command so that I can safely return to my previous screen. Almost all my applications which involve "network processing" are done like this and it works every time.
Hope I was clear with my explications, which might not be the case because here is kind of late :)
Mihai