We now have a compiling libtpproto-java on MIDP. We are now concentrating on building a little MIDP application to test that the library still works.
Sometime we will look at what needs to be merged back into mainline and how to make sure it doesn't interfere with normal java operation. Once that is completed we will be looking at writing a proper client for MIDP phones. Good work Brendan! Tim 'Mithro' Ansell On Tue, 2008-06-10 at 19:45 +0200, Krzysztof Sobolewski wrote: > Tuesday 10 of June 2008 05:38:03 Roberts, Brendan Matthew - robbm005 > napisał(a): > > > PipelinedConnection.java contains the use of BlockingQueues and > ExecutorServices that I'm unsure how to deal with and replace. Asmm > mentioned on IRC, that it may be possible to remove this class > outright in the creation of a client. Is this possible, why would it > be so? > > PipelinedConnection is used to write multithreaded programs and is > mostly just a convenience (although very convenient). You could indeed > remove it, if you can live with SimpleSequentialConnection and its > quirks ;) Another possibility is to find a backported > java.util.concurrent library and see if it of any use in MIDP. > > > Connection.java contains the use of a Future<Void> receiveAllFrames() > method. I'm unsure how to deal with this, or how to replace it with > something that would work in J2ME. > <snip> _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
