Fedora Server Role D-BUS API Design Discussion

Mon Mar 24 22:05:45 UTC 2014

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/24/2014 05:04 PM, Miloslav Trmač wrote:
> 2014-03-20 14:00 GMT+01:00 Stephen Gallagher <sgallagh at redhat.com 
> <mailto:sgallagh at redhat.com>>:
> 
>> I agree with these, but we may not want to '1.0' the api until
>> we are further along?
> 
> I'd like for clients to be backwards and forwards-compatible. So
> new versions of clients should be able to fall back to older,
> deprecated versions of the API and newer versions of the server
> should be able to support any version of the API that is still
> meaningful (such as we've added a new version of the API that gives
> more control, but the old version could still produce a usable
> system compatible with older releases).
> 
> 
> That requires us to know and specify in advance how would the
> server know which version of the API the client is indenting to
> use.  So, for the record, do we plan to just add methods (e.g.
> DeployV2) to the existing interfaces?

That's certainly the easiest (and most D-BUS-esque) way to do it. I'm
open to other suggestions, of course.