<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">+1 on Accept headers and also using the latest and greatest if no version is specified/<div><br></div><div>i believe this is what github also does<br><div><div>On Aug 28, 2014, at 4:36 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 2014-08-28, Matthias Wessendorf wrote:<br><blockquote type="cite">On Thu, Aug 28, 2014 at 10:14 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>><br>wrote:<br><br><blockquote type="cite"><br><br><br>On Thu, Aug 28, 2014 at 9:29 AM, Daniel Bevenius <<br><a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br><br><blockquote type="cite"><blockquote type="cite">If we go for the accept header and the consumer don't provide it, what<br></blockquote>do we do ? Return an error or use implicitly the latest version ?<br>Perhaps we can return the current version to not break any existing<br>clients. New clients will need to provide an explicit version.<br><br></blockquote>Why not but for how long do we return the "old" version by default ? (cf<br>my questions around deprecation)<br><br></blockquote><br>yep - I am for that: looks like I forgot, and I think we had that on our<br>face2face: no version == 1.0.0 (old)<br></blockquote><br>I vote for return the latest, instead of something old. And specify old<br>versions if you want to.<br><br><blockquote type="cite"><br>-M<br><br><br><blockquote type="cite"><br><blockquote type="cite"><br>On 28 August 2014 09:25, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br><br><blockquote type="cite">Some questions :<br><br>* If we go for the accept header and the consumer don't provide it, what<br>do we do ? Return an error or use implicitly the latest version ?<br>* What will be our deprecation policy ? Do we want keep maintaining all<br>the versions forever or let's say for 1.1 we still provide 1.0 and for 2.0<br>we drop 1.0 ?<br><br>About the implementation :<br>* I like the suggested CDI solution, if possible.<br>* Erik also mentionned OSGI and I'm -9999^99 to introduce that techno<br><br>Sebi<br>ps : I just read this blog post and it's really interesting :<br><a href="http://apiux.com/2013/05/14/api-versioning/">http://apiux.com/2013/05/14/api-versioning/</a><br><br><br><br>On Thu, Aug 28, 2014 at 8:07 AM, Daniel Bevenius <<br>daniel.bevenius@gmail.com> wrote:<br><br><blockquote type="cite">+1 For using the Accept header to specify the version in the media type.<br><br><br>On 28 August 2014 07:50, Matthias Wessendorf <matzew@apache.org> wrote:<br><br><blockquote type="cite">Hello,<br><br>for the 1.1.x (master) we are potentially doing some changes on the<br>Sender-API (see [1]).<br><br>However, for backwards compatibility we need to think about API<br>versioning.<br><br>For REST APIs there are (IMO) two options:<br>* accept header<br>* URIs<br><br>On our Face2Face meeting we briefly talked about this and I think the<br>"accept header" solution was the one that had most fans. I think QMX added<br>that it is better for migration. One thing we were not clear on (I think):<br>What are HATEOS defined semantics?<br><br><br>Besides the what (headers vs. URI), I think we should think about<br>possible implementations, to switch different versions.<br><br>Not sure, but wouldn't it be possible to inject an annotated<br>SenderService into the RESTful endpoint, based on header values ?<br>We could have a default impl (version 1.0.0) and an alternate one,<br>that is injected if the accept header indicate API version 1.1<br><br>Any thoughts ?<br><br>-Matthias<br><br><br>[1]<br>http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008881.html<br><br>--<br>Matthias Wessendorf<br><br>blog: http://matthiaswessendorf.wordpress.com/<br>sessions: http://www.slideshare.net/mwessendorf<br>twitter: http://twitter.com/mwessendorf<br><br>_______________________________________________<br>aerogear-dev mailing list<br>aerogear-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br>aerogear-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br>aerogear-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br><br>--<br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a><br></blockquote><br><blockquote type="cite">_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote><br><br>--<br><br>abstractj<br>PGP: 0x84DC9914<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></blockquote></div><br></div></body></html>