summaryrefslogtreecommitdiffstats
path: root/server/red_worker.c
diff options
context:
space:
mode:
authorAlexander Larsson <alexl@redhat.com>2010-08-26 15:14:05 +0200
committerAlexander Larsson <alexl@redhat.com>2010-09-02 10:22:41 +0200
commit0c6d654c2f67795fe5c3229bb615ab2bd99ef7a4 (patch)
tree20fa805160343ebedbeb3e61b726db3ecff67f7b /server/red_worker.c
parentfc2a84eb5beb4424d99121e2ed79c6bebefaf27e (diff)
downloadspice-0c6d654c2f67795fe5c3229bb615ab2bd99ef7a4.tar.gz
spice-0c6d654c2f67795fe5c3229bb615ab2bd99ef7a4.tar.xz
spice-0c6d654c2f67795fe5c3229bb615ab2bd99ef7a4.zip
Add API to turn on backwards compatibility mode
When upgrading a cluster of machines you typically do this by upgrading a set of machines at a time, making the new machines run the new software version, but in a fashion compatible with the old versions (in terms of e.g. migration). Then when all machines are upgrades, any new features in the new version can be enabled. This API allows qemu to limit the set of features that spice uses to those compatible with an older version, in order to do an upgrade like this. Right now it doesn't really do much, since we don't keep compat with 0.4.0 atm (although that may be added later). There is no guarantee that any future version of spice support being compatible with any previous version. However, we will always support compatibility with the previous major version so that clusters can be upgraded step by step.
Diffstat (limited to 'server/red_worker.c')
0 files changed, 0 insertions, 0 deletions