- Remove draft status
- Change default success response to be json-object
- Change error and event data member to be a json-object
- Update examples
- Add new section Compatibility Considerations
- Other fixes and clarifications
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
Luiz Capitulino lcapitul...@redhat.com writes:
[...]
-4. Notes to Client implementors
+4. Compatibility Considerations
+
-4.1 It is recommended to always start the Server in pause mode, thus the
-Client is able to
Markus Armbruster wrote:
While I think these promises are appropriate for a mature version of the
protocol, I do not think we should make them for 0.12.
We've just dreamed up version 0.1 of the protocol. It hasn't been used
in anger. Yes, we put some serious thought in it, and we even have
On Fri, 18 Dec 2009 11:44:27 -0600
Anthony Liguori aligu...@linux.vnet.ibm.com wrote:
Markus Armbruster wrote:
While I think these promises are appropriate for a mature version of the
protocol, I do not think we should make them for 0.12.
We've just dreamed up version 0.1 of the
On Fri, 18 Dec 2009 18:20:52 +0100
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino lcapitul...@redhat.com writes:
[...]
-4. Notes to Client implementors
+4. Compatibility Considerations
+
-4.1 It is
On Fri, 18 Dec 2009 19:06:18 +0100
Markus Armbruster arm...@redhat.com wrote:
Anthony Liguori aligu...@linux.vnet.ibm.com writes:
Markus Armbruster wrote:
While I think these promises are appropriate for a mature version of the
protocol, I do not think we should make them for 0.12.
Anthony Liguori aligu...@linux.vnet.ibm.com writes:
Markus Armbruster wrote:
While I think these promises are appropriate for a mature version of the
protocol, I do not think we should make them for 0.12.
We've just dreamed up version 0.1 of the protocol. It hasn't been used
in anger.
Luiz Capitulino lcapitul...@redhat.com writes:
On Fri, 18 Dec 2009 18:20:52 +0100
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino lcapitul...@redhat.com writes:
[...]
-4. Notes to Client implementors
+4. Compatibility Considerations
