<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 08/07/2015 07:04 PM, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:55C4B3F0.9090806@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 07/08/2015 02:19, Chandra Shehkhar
Reddy Potula wrote:<br>
</div>
<blockquote cite="mid:55C43FE3.30206@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Aline,<br>
<br>
As an end user I might not like switching the URI quite often as
developer keep changing them. It really defeat the purpose. <br>
</blockquote>
<br>
So do not update to a newer version!<br>
</blockquote>
I feel this may not be the right way to do if we want smooth
transition to the end user. End user can still use the old
functionality of certain feature's but at the same time seamlessly
pick up the functionality released in the new version for other
feature's !<br>
<blockquote cite="mid:55C4B3F0.9090806@linux.vnet.ibm.com"
type="cite"> <br>
<blockquote cite="mid:55C43FE3.30206@linux.vnet.ibm.com"
type="cite"> <br>
Regards<br>
Chandra<br>
<br>
<div class="moz-cite-prefix">On 08/07/2015 12:03 AM, Aline
Manera wrote:<br>
</div>
<blockquote cite="mid:55C3A860.50408@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 06/08/2015 07:41, Chandra
Shehkhar Reddy Potula wrote:<br>
</div>
<blockquote cite="mid:55C339D4.2070502@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Hi Aline,<br>
<br>
No need to mention explicitly, but this is very useful in
case where end users are exploiting functionality via REST
API directly and not UI way.<br>
</blockquote>
<br>
I suppose end users know which version he/she is using, right?
=)<br>
<br>
<blockquote cite="mid:55C339D4.2070502@linux.vnet.ibm.com"
type="cite"> <br>
Regards<br>
Chandra<br>
<br>
<div class="moz-cite-prefix">On 08/06/2015 01:52 PM, Chandra
Shehkhar Reddy Potula wrote:<br>
</div>
<blockquote cite="mid:55C3194D.3040208@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Hi Aline,<br>
<br>
Versioning helps you iterate faster and prevents invalid
requests from hitting updated endpoints. It also helps
smooth transitions over any major API version as you can
continue to offer old API versions for a period of time.
Definitely supporting the old version of API period of
time while offering new functionality with newer version
always give benefits and extra time for end user to adjust
to new one.<br>
<br>
I see lot of products in the market are adapting
versioning (see below link)<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.lexicalscope.com/blog/2012/03/12/how-are-rest-apis-versioned/">http://www.lexicalscope.com/blog/2012/03/12/how-are-rest-apis-versioned/</a><br>
<br>
I do understand the concern of maintaining the version of
the API endpoints , below are some of the links from
Openstack, which talks about it.<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://developer.openstack.org/api-ref.html">http://developer.openstack.org/api-ref.html</a><br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.openstack.org/wiki/VersionDiscovery">https://wiki.openstack.org/wiki/VersionDiscovery</a><br>
<br>
Hope it make senses to you.<br>
<br>
Regards<br>
Chandra<br>
<br>
<div class="moz-cite-prefix">On 08/06/2015 12:04 AM, Aline
Manera wrote:<br>
</div>
<blockquote cite="mid:55C25745.1000903@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
Hi Chandra,<br>
<br>
I don't see any benefit in adding the version in the
URL. Instead of that, it scares me on how we will
maintain it.<br>
<br>
Once we move to wok and Kimchi as plugin, all the APIs
will be automatically updated so everything will be in
the same page.<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<div class="moz-cite-prefix">On 17/07/2015 09:47,
Chandra Sr Potula wrote:<br>
</div>
<blockquote
cite="mid:OF5F31939B.F65133B3-ON65257E85.0044037D-65257E85.0046405F@in.ibm.com"
type="cite">
<p><font face="DejaVu Serif" size="2">Hi Kimchi/Ginger
Devel-Team,</font><br>
<br>
<font face="DejaVu Serif" size="2">Thank you for
creating WOK branch to separate the kimchi plugin
from the base frame work. It is a great idea.</font><br>
<br>
<font face="DejaVu Serif" size="2">Along with the
separation of kimchi plugin looks like there is a
transformation of REST API URIs as well. So
thinking in those lines will it be good idea even
to introduce version to the REST API URIs ?</font><br>
<br>
<font face="DejaVu Serif" size="2">Let me take one
REST API URI to convey clear on what I am talking
about.</font><br>
<br>
<font face="DejaVu Serif" size="2">To retrieve the
host repository information, current URI is:
"/plugins/kimchi/host/repositories".</font><br>
<br>
<font face="DejaVu Serif" size="2"><b>Recommendation</b></font><font
face="DejaVu Serif" size="2">:</font><br>
<font face="DejaVu Serif" size="2">New host
repository URI can look like : </font><font
face="DejaVu Serif" size="2"><b>"</b></font><font
face="DejaVu Serif" size="2"><b>/plugins/kimchi/v<version>/host/repositories"
, </b></font><font face="DejaVu Serif" size="2">so
that it is easy to maintain REST API future
enhancements at the same time do not brake some
body who is using the existing URI.</font><br>
<br>
<font face="DejaVu Serif" size="2">Note* Adding
version in the URI above is just an example and
we could place the version in the URI best
possible way.</font><br>
</p>
<p><font face="DejaVu Serif" size="2">Thanks and
Regards,</font><br>
<font face="Georgia" size="3" color="#888888"><b>Chandra
Shekhar Reddy Potula</b></font><font
face="Georgia" size="1" color="#00CCFF"><br>
Staff System Software Engineer<br>
IBM Systems & Technology Group, Systems
Software Development<br>
System z Firmware Development</font><font
face="serif" size="3"> </font>
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr valign="top">
<td colspan="2" valign="middle" width="650">
<hr align="left" size="2" width="100%"></td>
</tr>
<tr valign="top">
<td width="401"><font face="Georgia" size="1"
color="#466BB0"><b>Phone:</b></font><font
face="Georgia" size="1" color="#5F5F5F"> 91-080-4066-0786</font><font
face="Georgia" size="1" color="#466BB0"> |
</font><font face="Georgia" size="1"
color="#466BB0"><b>Mobile:</b></font><font
face="Georgia" size="1" color="#5F5F5F"> 91-973-1122-221</font><font
face="Georgia" size="1" color="#466BB0"><b><br>
E-mail:</b></font><font face="Georgia"
size="1" color="#5F5F5F"> </font><font
face="Georgia" size="1" color="#5F5F5F"><u><a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:chandra.shekhar@in.ibm.com"><a class="moz-txt-link-abbreviated" href="mailto:chandra.shekhar@in.ibm.com">chandra.shekhar@in.ibm.com</a></a></u></font></td>
<td width="249">
<div align="right"><img
src="cid:part5.06000600.07070407@linux.vnet.ibm.com"
alt="IBM" height="30" width="83"><font
face="Georgia" size="1" color="#5F5F5F"><br>
<br>
ORR, Manyatha MD3 1F B247<br>
Bengaluru, Karnataka 560045<br>
India</font></div>
</td>
</tr>
</tbody>
</table>
<font face="serif" size="3"> </font> <br>
</p>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>