Hi Michael,
two questions:
Can you elaborate on why you think there's no backwards compatibility
issues?
In your proposal, are you leaving /api/capabilites in place as it is
now? If not how to you enumerate the different versions?
Regards,
Geert
On 05/24/2012 09:53 AM, Michael Pasternak wrote:
the motivation:
===============
1. current design is not restfull
2. is not consistent with the rest of api impl.
impacts:
========
as this resource not used programmatically, we do not expect any
backward compatibility issues
planned change is:
=================
from:
http://localhost:8080/api/capabilities
<capabilities>
<version major="3" minor="1">
...
<version/>
<version major="3" minor="0">
...
<version/>
</capabilities>
to:
http://localhost:8080/api/capabilities/xxx
<capabilities>
...
</capabilities>
(where xxx is a version number)
--
Geert Jansen
Sr. Product Marketing Manager, Red Hat Enterprise Virtualization
Red Hat S.r.L. O: +39 095 916287
Via G. Fara 26 C: +39 348 1980079 (when in US: 415-623-0542)
Milan 20124, Italy E: gjansen(a)redhat.com