On 03/10/2011 06:42 PM, Anthony Liguori wrote:
Maybe for QMPv2, but for QMPv1, this is going to introduce an
extremely incompatible change.
Why? It's 100% backwards compatible.
It's a very significant change for clients. While technical
compatible, it would require a change to the client infrastructure to
support the new feature.
Yes. That's generally a good thing, you implement something at the
infrastructure level once instead of at a higher level N times.
I'm not saying we shouldn't make a change like this, but we should
minimize these type of changes.
I agree, so we should design the protocol well, without planned
obsolescence. We'll make some mistakes, but at least they'll be unplanned.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
