incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Davis <>
Subject Re: [QUESTION] Alternative way how to use Deltacloud
Date Tue, 15 Feb 2011 03:41:17 GMT
David Lutterkort <> wrote on 02/14/2011 08:23:37 PM:
> > It seems to me like a way how 'fog' or 'libcloud' is going and I'm not 
> > if we want to support this way as well.
> I don't want to go that way - we should stress that the value of
> Deltacloud lies in (a) the REST API and (b) that all the heavy lifting
> is done on the server, keeping the clients very simple.

  can you elaborate on this?  What's the benefit of the REST API?  It 
seem to me that the benefit is the abstraction layer above all of the 
regardless of whether its being presented via REST, Ruby, Java, or 
IMO, what people are looking for is the ability to talk to multiple 
with minimal specialization code.  Seems to me that offering them the 
of an http-hop model vs a client-side-adapter model should be left up to 
client to decide.  Not everyone likes or can support a multi-hop model.
Either way, let them make the choice but whatever they choose give them 
benefits of the DeltaCloud engine.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message