API versioning was discussed here in this thread: Versioning Stratos REST API
On Wed, Nov 5, 2014 at 7:57 AM, Imesh Gunaratne <im...@apache.org> wrote: > IMO we should not change the REST API of a released version unlesss it is > unavoidable. We need to introduce a new version of the API for the new > release and do the modifications there. The old API versions we can > deprecate and remove after certain releases/time. > > I will introduce API version handling logic and will check the possibility > of preserving the 4.0 API. > > On Wed, Nov 5, 2014 at 8:05 AM, Udara Liyanage <ud...@wso2.com> wrote: > >> Hi Jeffrey, >> >> Yes I changed the REST API response format. There is a mailing thread to >> discuss this also. >> Response text is empty for most success POST API invocations. But HTTP >> status code is sent as 200/201/204 depending on the scenario. Additionally >> location header will contain the Url of the created resource. >> >> Yes we need to document this. Will update the docs. >> >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> > > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
