From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: Domain Save Image Format proposal (draft B) Date: Tue, 11 Feb 2014 17:28:43 +0000 Message-ID: <21242.24011.946144.811862@mariner.uk.xensource.com> References: <52F90A71.40802@citrix.com> <21242.21650.571988.662930@mariner.uk.xensource.com> <52FA5992.3070207@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52FA5992.3070207@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: Shriram Rajagopalan , Stefano Stabellini , Ian Campbell , "Xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org David Vrabel writes ("Re: Domain Save Image Format proposal (draft B)"): > On 11/02/14 16:49, Ian Jackson wrote: > > I greatly prefer doing forward-compatibility with new record type > > enums etc. than with version numbers. Version numbers presuppose a > > strict global order on all the implementations' capabilities, which is > > of course not necessarily true in free software. > > I think I quite like this idea. There would still need to be a central > repository of record types. Right. One thing you can do is like PNG and have separate ranges of record type numbers for (a) ok to ignore this if not understood and (b) fatal if not understood. I think PNG also has subset of the namespace for "private use". Ian.