>James raises a good point:
>
>> I think it is the real-time nature of Embedded programming that puts
>> people in a bit of a spin.
>
>I've been thinking about this. Creation of a container implementation that
can
>support real-time (in the strict, embedded sense of the word) is a very
difficult
>task.
Scheduling of multiple threads is the only place that predictable latencies
get shot down. Realtime only requires predictable latencies to design a
system that provides the required functionality. RTSJ is primarily about
resolving this issue. GC is another problem that RTSJ addresses by making it
possible to designate threads as non-garbage generating. Thus, the scheduler
will still allow them to meet their schedules because the GC process won't
need to lock them out of the CPU...
So, if you design with RTSJ in mind, you should have no problems putting
embedlets into an RTSJ compatible VM...
-----
gr...@cy... (Cyte Technologies Inc)
|
