On Feb 23, 2011, at 6:49 PM, Felipe Cardoso Martins wrote:

> Michal,
> 
> what do you think about?

I just meant where we should put client code for 'other languages', like Python 
or
PHP in reaction to David.

 -- Michal 

> /
> /server
> /client
> /client/ruby
> /client/python
> /client/php
> 
> I begin write yesterday a extension of Zend_Service like
> Zend_Service_Amazon_EC2...
> 
> []'s
> 
> On Wed, Feb 23, 2011 at 8:44 AM, Michal Fojtik <[email protected]> wrote:
>> On 22/02/11 17:59 -0800, David Lutterkort wrote:
>>> 
>>> On Tue, 2011-02-22 at 15:09 +0100, Michal Fojtik wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> Recently I created a small and simple (thus stupid;) Python client for
>>>> Deltacloud API.
>>>> 
>>>> It has just very basic and limited functionality but you can launch an
>>>> instance, or list images.
>>>> 
>>>> I hope someone will pickup up this and improve it (add more
>>>> functionality).
>>>> 
>>>> https://github.com/mifo/deltacloud-python
>>> 
>>> How about just sticking that into the Apache deltacloud repo ? For the
>>> time being, I think it would be best to have all the clients in the main
>>> repo.
>> 
>> Definitely good idea +1. Will sent a patch with this client. What about
>> directory structure? Should we do something like:
>> 
>>  /
>>  /server
>>  /client
>>  /python
>>  /php
>> 
>> or you have better idea?
>> 
>>  -- Michal
>> 
>>> 
>>> Of course, that will trigger a complex search for the right directory ;)
>>> 
>>> David
>>> 
>>> 
>> 
>> --
>> --------------------------------------------------------
>> Michal Fojtik, [email protected]
>> Deltacloud API: http://deltacloud.org
>> --------------------------------------------------------
>> 
> 
> 
> 
> -- 
> Abraço,
> 
> Felipe Cardoso Martins
> [email protected]
> http://www.linkedin.com/in/felipecardosomartins
> 
> “O segredo do prazer no trabalho pode ser resumido em uma palavra: excelência.
> Saber como fazer bem algo é ter prazer nisso. ”
> Pearl Buck

Michal Fojtik
Software Engineer, Deltacloud API project
http://www.deltacloud.org
[email protected]


Reply via email to