Sim IJskes - QCG wrote:
available through Jini services. The real time service might remove
its entry from lookup once it has reached a load level that limits
the real time guarantees. There are a number of time guarantees that
need to be considered, such as network latency (according to the
doc's EtherCAT has low latency, distance and load are limiting
factors) and Service load.
Thats a particular nice thought, but if a service cannot comply with
its realtime constraints, how can we make sure it has the capacity to
remove itself?
Good point, one must know in advance how many clients could be supported
at peak load, without consuming the capacity required to request removal
from registrar's. This is a platform dependant constraint.
N.B. Here's some more info about RTSJ's capabilities:
http://www.youtube.com/watch?v=xH1yUXd9krU
http://www.youtube.com/watch?v=g5Ky2ApC4Y4&feature=PlayList&p=49D5E0AD38A46407&index=20
http://www.youtube.com/watch?v=-CuVVZq9GfY&feature=PlayList&p=49D5E0AD38A46407&index=21
Cheers,
Peter.
