Runtime software upgrades
The requirements for non-stop software systems is increasing and has been for the
last decade. The requirements grow in number of applications, as well as in what
functionality a non-stop system is required to present and in the quality and
reliability aspects of what it does.
Runtime upgrading of software (software hot swap) is possible in many major
applications today. This ability is designed and implemented by hand for each
application, and even the top level applications have to be designed with this in
mind. There is no sound research foundation for building this type of systems.
I propose a study on what the design patterns of non-stop software systems are
and how applications can describe, divide, and transfer their state. Is there a
programming model for an interesting class of applications that can relieve the
top level applications from hot swap awareness and turn hot swapping into a
middleware issue? Is there a way to tell if the software upgrade will be
Place: Information technology, Uppsala University
Room 1510 is in Building 1, Floor 5, room 10
(in the southern part of the building).
Help on how get here and
MIC campus drawing.
There will be an extended period for discussions after the seminar.
Speakers are encouraged to give an short (5 min) introduction to the subject at the begining of the talk.
Listeners are excused if they have to leave after 15.00.
Updated 24-Nov-2000 14:23 by Roland Grönroos
e-mail: info -at- astec.uu.se