cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satoshi Kobayashi <satosh...@stratosphere.co.jp>
Subject Re: [javelin] Updates on javelin...
Date Wed, 21 Nov 2012 02:01:19 GMT
Hi Alex,

2012/11/21 Alex Huang <Alex.Huang@citrix.com>:
>> It is planning to use jax-rs to implement internal API? Or is it
>> certain CloudStack API now?
>
> Please reference https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Refactoring
>
> All of that work is being done in the javelin branch
>
> In here, jax-rs is used as an api for cloud-engine which is not end user facing.
>>
>> If It is the latter:
>> I think that it may not necessarily be suitable for implementing Query
>> API. I think that it just matches if there is a plan to refactor into
>> RESTful more which throw away backward compatibility. (ex. Resource
>> structure is made to a layer).
>>
>> But I have not an alternative idea. This may only be my overanxiety. I
>> think that I am good, if CloudStack API is refactored.
>
> We are refactoring the end user API but we're not going to change the over the wire representation.
 What we are changing are the annotations and packaging and documentation to make it easier
for people to understand.  The spec for that is here.

Thanks. I read the document and the code.

>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+refactoring
>>
>> BTW, what is Javelin branch? It seems a branch for refactoring.
>>
>> >
>> > --Alex
>> >
>> >

Mime
View raw message