<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014年02月28日 00:05, Dan Smith wrote:<br>
</div>
<blockquote cite="mid:530F622D.5050203@danplanet.com" type="cite">
<blockquote type="cite">
<pre wrap="">Sure, but that's still functionally equivalent to using the /v2 prefix.
So we could chuck the current /v3 code and do:
/v2: Current thing
/v3: invalid, not supported
/v4: added simple task return for server create
/v5: added the event extension
/v6: added a new event for cinder to the event extension
and it would be equivalent.
</pre>
</blockquote>
<pre wrap="">
Yep, sure. This seems more likely to confuse people or clients to me,
but if that's how we decided to do it, then that's fine. The approach to
_what_ we version is my concern.
</pre>
</blockquote>
<br>
Does mean our code looks like as below?<br>
if
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
client_version > 2:<br>
....<br>
elif client_version > 3<br>
...<br>
elif client_version > 4:<br>
...<br>
elif client_version > 5:<br>
...<br>
elif client_version > 6:<br>
..<br>
<br>
And we need test each version... That looks bad...<br>
<br>
<blockquote cite="mid:530F622D.5050203@danplanet.com" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">And arguably, anything that is a pure "add" could get away with either a
minor version or not touching the version at all. Only "remove" or
"modify" should have the potential to break a properly-written application.
</pre>
</blockquote>
<pre wrap="">
Totally agree!
--Dan
_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>