From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.68.191.233 with SMTP id hb9csp85946pbc; Wed, 30 May 2012 13:36:30 -0700 (PDT) Received: by 10.182.2.193 with SMTP id 1mr16588557obw.46.1338410189553; Wed, 30 May 2012 13:36:29 -0700 (PDT) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id xg4si458713obb.144.2012.05.30.13.36.29; Wed, 30 May 2012 13:36:29 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C1FC73B006; Wed, 30 May 2012 20:36:28 +0000 (UTC) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id 412BA3AFF7; Wed, 30 May 2012 20:36:08 +0000 (UTC) Received: by wgbfg15 with SMTP id fg15so181585wgb.23 for ; Wed, 30 May 2012 13:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=H1T9du768Sc3df9HJkE42eQ9MPdh7u2PD6bxkolKy+E=; b=Otb1qr53MCcgjZ376Qee3b8xjBUp+ervfijHodoINE9Zhd6vv9cH5gSHvtZjlHdwK+ AAZXCpI+BG/sUOi4Qu0AqF4I9ZeAna74AXsIiCR1puwx4YshLlM2M60szHJOt+HMphrX eZI8osoonVGfSVwTWQ5IefkO8VeTugMQdehKzE1fPpkNLHJQi2Huj6J5WMED0JDHk3Mt uMNjTJYcazRop8TRfntCyvPbiq1OeF36ZHUItZfsrTx7jn/hiCGkDGY6i4p2GwwbcLlU aG5ssmG43vusGgzHLZWHwWU5tDnStCt+OQl9pCxaR6QVwGrUrWLwrn6cXDB2PkUjDKzx 3X4Q== Received: by 10.216.213.22 with SMTP id z22mr10420164weo.184.1338410167462; Wed, 30 May 2012 13:36:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.161.212 with HTTP; Wed, 30 May 2012 13:35:46 -0700 (PDT) From: Matthieu Rakotojaona Date: Wed, 30 May 2012 22:35:46 +0200 Message-ID: To: sup-devel , sup-talk Subject: [sup-talk] Documentation of the heliotrope API X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hello everyone, While browsing the interwebs, I realized that many people are also tired of the cumbersomeness of the IMAP protocol, and a few of them has started some work on implementing what they would love to see. For instance, you can find a thread talking about it in [0] which links to a few other thoughts. What is interesting is that many people have the same approach to use JSON-over-HTTP in a RESTful manner. I think each of these implementations' problem is the same: they lack visibility to gather improvements. Seeing this, I thought that to give Heliotrope a little more visibility, we should improve the documentation a little bit. I have started [1] by the first step: the API. Feel free to comment back on this, or fork/edit the pages yourself. Cheers, -- Matthieu RAKOTOJAONA [0] http://blog.gaborcselle.com/2010/02/how-to-replace-imap.html [1] https://github.com/rakoo/heliotrope/wiki/A-brief-overview-of-the-heliotrope-api _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk