Re: Re: java xAPlib bug

[Jon Payne <jgpayne@xxxxxxxxxxxxxx>]

Not painful really, just back to the good old days ;-) of actually
needing to be careful of cpu and memory consumption!

I orginally bought the old 390 version TINI to do caller id decoding and
announcing about 5 years ago, cost 55gbp I think.  I'm pushing the 390 to
do so much I suppose: scanning for arrival/departure of 1-wire devices,
temperature gathering, web serving, call id decoding and announcing, and
anything else I can fit in! But if it doesn't need to be super quick, and
none of this does, then it's great. The newer 400 version probably wouldn't
break a sweat. I think it's a fantastic platform to work on, having the
rich Java libraries to work with and it being so cheap you can afford to
have several if needed. But the biggest advantage is being able to use
Java. I'm a C++ programmer by trade but I love using Java on the TINI, once
you get over the initial wierdness of using Java on such a low powered
platform (relative to a PC).

I can thoroughly recommend the TINI.

----- Original Message ----
From: Shaf Ali <shaf@xxxxxxx>
To: xAP_developer@xxxxxxx
Sent: Wednesday, 28 February, 2007 1:54:37 AM
Subject: Re: [xAP_developer] Re: java xAPlib bug


Jon Payne wrote:
> Hi Shaf,
>
> I think I too found those issues, but it was ages ago and I've
reworked this quite a bit because I'm using a TINI (embedded system) which
uses Java1.1/1.2 so I've changed things to use the older collections
libraries and also to make sending of xap messages more efficient (will
several processes running the creation and sending of one xap message takes
about 1 second!)
>
That sounds painful Jon. Was there any reason for choosing TINI ?

Looking at it - it does seem to be a very under powered platform. My
miniITX is fast but not sure if it can handle a JVM yet though - Java is
heavy.