Nirvana clients automatically
handle disconnect and reconnection to any number of Nirvana
servers. Should a Nirvana server disappear from the Nirvana
namespace the client will automatically try to connect
to the next defined Nirvana server.
In a single server scenario upon receipt of an abnormal
disconnection a Nirvana client will automatically try
to reconnect. The back-off period and interfaces handling
reconnection are all fully exposed in a public API.
They can be used to trigger off any number of specific
events.
Nirvana is also fully compatible with high availability
and business contingency products implemented within
the underlying operating system. This means that Nirvana
is compatible with existing HA/BCP policies as well
as providing its own in build fail over functionality.