On Thu, Jan 31, 2013 at 5:28 AM, Prasanna Santhanam <t...@apache.org> wrote: > On Thu, Jan 31, 2013 at 12:44:36AM +0530, Rohit Yadav wrote: >> I want to propose that we deprecated the current non-RESTful APIs and >> api server over next few months, year, 2 years... (let's vote on the >> timeline, what do you think should be duration for maintaining old set >> of apis?). And, we work on a maintainable REST-ful api server using >> JAX-RS (suggest any other technology)? >> >> Issues: >> https://issues.apache.org/jira/browse/CLOUDSTACK-638 >> https://issues.apache.org/jira/browse/CLOUDSTACK-1093 > > +1 > > a) Will both methods query and REST be supported via different > endpoints while the deprecation is happening?
We should keep the same parent endpoint, like host:port/client/api or /api. > > b) Is the plan to reuse existing API entities, which surface to a > query endpoint naturally over a REST endpoint, or do you plan to > re-write the API entities? I've some ideas, but I'll try to research possible ways of doing that, present them and maybe a POC to our community for feedback, flames and suggestions before I start working on it. > > For eg: CreateEntity, DeleteEntity, ListEntity over > > @Http(method=GET)Entity.list(), @Http(method=POST/PUT)Entity.create(), > @Http(method=DELETE)Entity.delete() > > c) An alert to downstream projects may be when you start this? - > jclouds, libcloud etc Sure. > > > -- > Prasanna.,
