I definitely would like to see some time spent on redesigning the simplicity of
lease renewal as it currently works, into something that was, in fact much more
reliable in volatile networks. A moving renewal time that was based on visible
latency would be a good thing, even with a simple strategy such as averaging.
But a PID loop kind of renewal algorithm could be nice as it would nudge the
speed based on response time. PID is the automation mechanism that is used for
maintaining temperatures and flows based on perceived reaction of the system to
control operations.
Gregg Wonderly
Kúti Zsolt wrote:
Hi all!
Browsing around I bumped into an interesting Jini-based
distributed directory service (FADA) that is an essential part of
a highly ambitous project, called Digital Ecosystem (DBE).
This writing is about how they tailored FADA lease mechanism to their
needs. I think, this can be useful for River itself, too.
Avoiding JINI lease failures using the Kalman Filter
http://engineeryourdreams.blogspot.com/2009/01/avoiding-jini-lease-failures-using.html
Anyone encountered with a scenario that is described above?: on
networks where delays can unpredictably vary, a lease may fail because
its renewal reaches too late its destination.
Zsolt
