From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.50.5 with SMTP id x5cs89395wfx; Tue, 21 Jun 2011 10:19:54 -0700 (PDT) Received: by 10.224.189.72 with SMTP id dd8mr5605870qab.182.1308676793915; Tue, 21 Jun 2011 10:19:53 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u29si9190452qcs.123.2011.06.21.10.19.53; Tue, 21 Jun 2011 10:19:53 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 4E728177994F; Tue, 21 Jun 2011 13:19:53 -0400 (EDT) Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by rubyforge.org (Postfix) with ESMTP id EA1E11858346 for ; Tue, 21 Jun 2011 13:17:00 -0400 (EDT) Received: by pwj1 with SMTP id 1so100366pwj.23 for ; Tue, 21 Jun 2011 10:17:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=lENrCfNBi4RkFU+xl1tDQ1hzhJexU6R3M1n2k9H28Bc=; b=UbjpLapSMbpZOcirTH/suUDntlHDnhGDURlWu8iGyGgHRUgli82T16o0kWg3eIt1Jy XWG5Kf3WOnVfgtiQWy5ldex1HPDfmXXZR0i0PxHU+RqfDftscRvWcw5m/TPZV1ipx83U sWRJvksOkBCbZSMbVqJqLewypQ6pbxDaOaBA0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=lsTEJCmAxr4RXvZCRVcmMBGOUCU12j5fJ2na+gUhdHTTpFD28UTpqzC4w36B/vixMo 6Nlz/+ZyIXbmS8DXHtp5tOVpPjH4xRF2b3ixzEyebFu7pD91zNMaSfLFxAr/dFJuwrpI LHnbs5xaGrsS/uRvRUf0bTY9vppkHmXTDZqBo= Received: by 10.68.17.99 with SMTP id n3mr3168825pbd.351.1308676620121; Tue, 21 Jun 2011 10:17:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.51.170 with HTTP; Tue, 21 Jun 2011 10:16:45 -0700 (PDT) In-Reply-To: <1308520505-sup-4762@masanjin.net> References: <1308520505-sup-4762@masanjin.net> From: Vivien Didelot Date: Tue, 21 Jun 2011 13:16:45 -0400 Message-ID: To: William Morgan Cc: notmuch , Sup developer discussion Subject: Re: [sup-devel] Turn Turnsole into a generic mail client X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0745826070==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============0745826070== Content-Type: multipart/alternative; boundary=bcaec52161f11176fb04a63c05b9 --bcaec52161f11176fb04a63c05b9 Content-Type: text/plain; charset=ISO-8859-1 Hi William, I'm not suggesting to make Heliotrope supports several clients (what it already does via provinding JSON), I'm suggesting the make the Turnsole interface modulable to several mail sources. And its default and official one will be the Heliotrope client for sure. I hope it is clearer. On Sun, Jun 19, 2011 at 6:01 PM, William Morgan wrote: > Hi Vivien, > > Reformatted excerpts from Vivien Didelot's message of 2011-06-19: > > As Turnsole is a great mail interface, I was thinking about having it > > generic to multiple servers or mail sources, to fit many use cases. > > > > Explicitely, the Turnsole::Client class ( > > https://github.com/wmorgan/turnsole/blob/master/lib/turnsole/client.rb) > > could be turned into a Turnsole::Client module instead, > > The server portion of turnsole, heliotrope, is explicitly designed to > support multiple clients and provides a JSON-over-HTTP interface for > that purpose. > > The specifics of the protocol are still subject to change, but see e.g. > https://github.com/wmorgan/heliotrope/blob/master/lib/heliotrope-client.rb > for the ruby client that turnsole uses to communicate with the server. > -- > William > -- Vivien Didelot, vivien.didelot.org --bcaec52161f11176fb04a63c05b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi William,

I'm not suggesting to make Heliotrope supports sever= al clients (what it already does via=A0 provinding JSON),
I'm sugges= ting the make the Turnsole interface modulable to several mail sources.
And its default and official one will be the Heliotrope client for sure.
I hope it is clearer.

On Sun, Jun 19= , 2011 at 6:01 PM, William Morgan <wmorgan-sup@masanjin.net> wrote:
Hi Vivien,

Reformatted excerpts from Vivien Didelot's message of 2011-06-19:
> As Turnsole is a great mail interface, I was thinkin= g about having it
> generic to multiple servers or mail sources, to fit many use cases. >
> Explicitely, the Turnsole::Client class (
> https://github.com/wmorgan/turnsole/blob/mas= ter/lib/turnsole/client.rb)
> could be turned into a Turnsole::Client module instead,

The server portion of turnsole, heliotrope, is explicitly designed to=
support multiple clients and provides a JSON-over-HTTP interface for
that purpose.

The specifics of the protocol are still subject to change, but see e.g.
https://github.com/wmorgan/heliotrope/blob/ma= ster/lib/heliotrope-client.rb
for the ruby client that turnsole uses to communicate with the server.
--
William <wmorgan-sup@masanji= n.net>



--
Vivien Didelot,<= br>vivien.didelot.o= rg
--bcaec52161f11176fb04a63c05b9-- --===============0745826070== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============0745826070==--