Hi, API versioning is not yet implemented yet. So will introduce new API @Imesh may be able to provide a better answer here.
On Wed, Nov 5, 2014 at 11:42 PM, Jeffrey Nguyen (jeffrngu) < [email protected]> wrote: > > Thanks Udara for confirming. Can you let us know if us know if you're > going to restore the old behavior and introduce new API or you're going to > keep the new behavior? > > Thanks, > -Jeffrey > > > From: Imesh Gunaratne <[email protected]> > Date: Tuesday, November 4, 2014 11:57 PM > To: dev <[email protected]> > Cc: jeffrngu <[email protected]>, Mariangela Hills <[email protected]> > Subject: Re: Stratos Rest APIs that send empty response in 4.1 > > 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 <[email protected]> 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 > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897
