[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How to know what's supported in REST service 1.1?



Hi Lili

thanks for the feeback. There's still 1 advice I'd love to get:
So if I get things right, we should expect the cases where properties get removed or change semantically. I guess that we'd only be able to support this by having distinct client-libs for the different versions, right?

Cheers
André
On 09/04/2012 08:07 PM, Lili Nader wrote:
OpenStack's guideline (http://wiki.openstack.org/APIChangeGuidelines) does a good job of summarizing the presumptions we have been operating under so I'm glad to hear this works for you.

I wasn't referring to that bug but yes that is a good example of changing the semantics of a property.
Lili


----- Original Message -----
From: "André Dietisheim" <adietish redhat com>
To: "Lili Nader" <lnader redhat com>
Cc: "Xavier Coulon" <xcoulon redhat com>, dev lists openshift redhat com, "Krishna Raman" <kraman redhat com>, "Bill DeCoste" <bill decoste jboss com>
Sent: Friday, August 31, 2012 3:54:29 PM
Subject: Re: How to know what's supported in REST service 1.1?


On 08/31/2012 10:50 PM, Lili Nader wrote:


Hi Andre,

Usually, if the change is additive (meaning we add new attributes or resources) we do not increment the version number and the new information is still available in the old version.
ok. so that would mean that changes that remove properties or change semantics would get pushed to API 1.1, right?
I hope that there wont be too many of them. I'm currently thinking about how the openshift-java-client would support 1.0 and 1.1 (to be able to talk to a 1.0 server at X and 1.1 server at Y) and I currently dont see any golden hammer that would get fail-safe for all kind of changes. The most fail-safe approach would be to drop the strictly typed objects and replace them by loosely typed maps/collections. To be honest I'd love to avoid this if possible. Solved in a less fail-safe but still strictly typed manner would be to provide distinct object hierarchies for the different protocol versions. I'd love if you had some thoughts/hints to share.
Googling for advices on evolution of RESTful API's I found a guide for OpenStack: http://wiki.openstack.org/APIChangeGuidelines
I'd hope that we could stick to something equivalent, since this would make my live much easier. Would you agree/disagree?



I did a search through the code and it seems the only difference between 1.0 and 1.1 is the information returned for a cartridge.  The major difference seems to be the properties attribute returned in 1.0 versus 1.1.
Thanks for looking this up!
You're referring to https://bugzilla.redhat.com/show_bug.cgi?id=838611 right?



Lili


----- Original Message -----
From: "André Dietisheim" <adietish redhat com> To: Dev ex-elb1-prod-1847871222 us-east-1 elb amazonaws com , "Lili Nader" <lnader redhat com> , "Krishna Raman" <kraman redhat com> Cc: "Xavier Coulon" <xcoulon redhat com> Sent: Friday, August 31, 2012 12:56:11 AM
Subject: How to know what's supported in REST service 1.1?

Hi

Is there any way for us to find out what differs in 1.1 vs. 1.0 protocol
for the REST service?

Thanks
André


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]