skip to content »

Dynamic software updating java

dynamic software updating java-17

In the event of a failure, the hot spare would take over, and the main machine would become the new hot spare. In the event of an update, the hot spare would activate, the main system would update, and then the updated system would resume control.

dynamic software updating java-33dynamic software updating java-74dynamic software updating java-62dynamic software updating java-6

This is because Ksplice primarily targets security changes, rather than general updates.Current operating systems and programming languages are typically not designed with DSU in mind.As such, DSU implementations commonly either utilize existing tools, or implement specialty compilers.Since few programs are written with support for dynamic updating in mind, retrofitting existing programs is a valuable means of evaluating a DSU system for practical use.The problem space addressed by dynamic updating can be thought of as an intersection of several others.The earliest precursor to dynamic software updating is redundant systems.

In a redundant environment, spare systems exist ready to take control of active computations in the event of a failure of the main system.

These compilers preserve the semantics of the original program, but instrument either the source code or object code to produce a dynamically updateable program.

Researchers compare DSU-capable variants of programs to the original program to assess safety and performance overhead.

In computer science, dynamic software updating (DSU) is a field of research pertaining to upgrading programs while they are running. However, researchers have developed a wide variety of systems and techniques for implementing DSU.

These systems are commonly tested on real-world programs.

Examples include checkpointing, dynamic linking, and persistence.