Return-Path: Delivered-To: apmail-incubator-libcloud-archive@minotaur.apache.org Received: (qmail 5676 invoked from network); 21 May 2010 15:43:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 May 2010 15:43:01 -0000 Received: (qmail 33655 invoked by uid 500); 21 May 2010 15:43:01 -0000 Delivered-To: apmail-incubator-libcloud-archive@incubator.apache.org Received: (qmail 33559 invoked by uid 500); 21 May 2010 15:43:01 -0000 Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: libcloud@incubator.apache.org Delivered-To: mailing list libcloud@incubator.apache.org Received: (qmail 33551 invoked by uid 99); 21 May 2010 15:43:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 May 2010 15:43:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ianbicking@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 May 2010 15:42:56 +0000 Received: by gwj19 with SMTP id 19so492547gwj.6 for ; Fri, 21 May 2010 08:42:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=4akJIs3UlP76MTx+r89XsX2SDWpbYRKs2FR5S9DjgzI=; b=p0bO9H26rrzKWt418Ig3atkFYil25wilFM86qaIFyS8tiCQUBKIdpRz4SbFBdRlsGs LEltRD/4WqQbcCvzSsgpDgU5DwrM4ImZdEIvCH8z52GifuCb91REXFk12mtgFDIc+s/i pFTcNHVZFuGs+QnkcitiBE/+dDsh5FOOetJCE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=epZdRNXvR2ppfa+3kWfJXnbvFFZW438fB4wXt812oGB0XzzaZ/PUKm+HRkOe4SqP1E VT/7RqVy59xICPnFjD34a9qqd+Tbc1aU4ke6kLo9C8EeAOs7ib3XiJmOhzta44SL2fSP UGsMP+hBXcFAvv5dUr6qQxhM19n6nBZtt/9Vs= Received: by 10.91.65.20 with SMTP id s20mr1108815agk.33.1274456554151; Fri, 21 May 2010 08:42:34 -0700 (PDT) MIME-Version: 1.0 Sender: ianbicking@gmail.com Received: by 10.90.72.5 with HTTP; Fri, 21 May 2010 08:42:14 -0700 (PDT) From: Ian Bicking Date: Fri, 21 May 2010 10:42:14 -0500 X-Google-Sender-Auth: 98PwEhJwDz6zxkw5uBHXqPESXG0 Message-ID: To: libcloud@incubator.apache.org Content-Type: multipart/alternative; boundary=001485f86eea31225004871c8aab Subject: [libcloud] Are people using libcloud with non-Python environments? --001485f86eea31225004871c8aab Content-Type: text/plain; charset=UTF-8 Given recent discussion, I'm curious: is there anyone using libcloud from a non-Python environment, and if so, how? And how is it going? E.g., running it with Jython, or in a subprocess, or with separate servers, or... whatever? It seems like there's two basic motivations underlying this discussion: 1. People who don't use Python want access to what libcloud does 2. People who don't use Python want a codebase they can feel comfortable with and contribute to And then there's just some language politics. I feel like the perspective so far in these threads has been mostly from 2 and not 1. And the answers to these two motivations are pretty different. If you want access to what libcloud does (1), probably the first thing to work on would be some serialized protocol for the objects and methods in libcloud (e.g., JSONRPC). If you want to write other implementations (2), probably the first thing to work on would be language-neutral tests (making the tests more data-drive). -- Ian Bicking | http://blog.ianbicking.org --001485f86eea31225004871c8aab--