> I am not saying RESTful API will solve everything, but the follow the RESTful
> paradigm may help to clean up the APIs.
> For example, we have AddHostCmd and CreateStoragePoolCmd, the
> verb(Add and Create) may cause confusion. While if using RESTful API, POST
> is the well defined verb for this
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Thursday, April 04, 2013 3:29 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] RESTful API for CloudStack agents
>
> > We made a messy cloudstack API already, and it's
> We made a messy cloudstack API already, and it's hard to get rid of it, as a
> lot
> of clients((UI/marvin/jcloud, other cloudstack bindings)) are using this APIs
> already.
> We shouldn't make the mistake again, assuming that only AgentManager will
> use this agent APIs.
>
First, I don't thin
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Thursday, April 04, 2013 7:19 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] RESTful API for CloudStack agents
>
> That's true. I don't believe the design itse
On Apr 4, 2013, at 9:38 AM, Chip Childers wrote:
> On Thu, Apr 04, 2013 at 11:44:33AM +0100, Donal Lafferty wrote:
>> Sorry for the delay in responding.
>>
>> The GET / POST limit to HTTP verbs simplifies exposing the agent with HTML
>> forms. Using these verbs the agent interface can be expo
d.com]
> > Sent: Thursday, April 4, 2013 6:39 AM
> > To: dev@cloudstack.apache.org
> > Cc: cloudstack-...@incubator.apache.org
> > Subject: Re: [DISCUSS] RESTful API for CloudStack agents
> >
> > On Thu, Apr 04, 2013 at 11:44:33AM +0100, Donal Lafferty wrote:
compromise.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, April 4, 2013 6:39 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-...@incubator.apache.org
> Subject: Re: [DISCUSS] RESTful API for CloudStack agents
>
On Thu, Apr 04, 2013 at 11:44:33AM +0100, Donal Lafferty wrote:
> Sorry for the delay in responding.
>
> The GET / POST limit to HTTP verbs simplifies exposing the agent with HTML
> forms. Using these verbs the agent interface can be exposed via HTML forms
> should the developer want to use a b
incubator.apache.org
> Subject: Re: [DISCUSS] RESTful API for CloudStack agents
>
> On Tue, Apr 02, 2013 at 03:14:46PM -0400, Sebastien Goasguen wrote:
> >
> > On Apr 2, 2013, at 3:00 PM, Donal Lafferty
> wrote:
> >
> > > Could I get some feedback on the follo
; Sent: Tuesday, April 2, 2013 12:00 PM
> To: cloudstack-...@incubator.apache.org
> Subject: [DISCUSS] RESTful API for CloudStack agents
>
> Could I get some feedback on the following strategy for mapping CloudStack
> RPC commands to HTTP requests?
>
> The general approach is t
On Tue, Apr 02, 2013 at 03:14:46PM -0400, Sebastien Goasguen wrote:
>
> On Apr 2, 2013, at 3:00 PM, Donal Lafferty wrote:
>
> > Could I get some feedback on the following strategy for mapping CloudStack
> > RPC commands to HTTP requests?
> >
> > The general approach is to:
> > 1. map each cate
On Apr 2, 2013, at 3:00 PM, Donal Lafferty wrote:
> Could I get some feedback on the following strategy for mapping CloudStack
> RPC commands to HTTP requests?
>
> The general approach is to:
> 1. map each category of command to a URL. Each category corresponds roughly
> to a resource type b
Could I get some feedback on the following strategy for mapping CloudStack RPC
commands to HTTP requests?
The general approach is to:
1. map each category of command to a URL. Each category corresponds roughly to
a resource type being manipulated.
E.g. /cloudstack/latest/storagepool/
2. make th
13 matches
Mail list logo
