From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.134.218 with SMTP id k26cs22117bkt; Fri, 4 Jun 2010 10:32:10 -0700 (PDT) Received: by 10.231.148.73 with SMTP id o9mr14039075ibv.21.1275672729774; Fri, 04 Jun 2010 10:32:09 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id d1si2576904ibg.55.2010.06.04.10.32.08; Fri, 04 Jun 2010 10:32:09 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 835D61858375; Fri, 4 Jun 2010 13:32:08 -0400 (EDT) Received: from athena.silentflame.com (athena.silentflame.com [212.13.194.60]) by rubyforge.org (Postfix) with ESMTP id 2D3131858351 for ; Fri, 4 Jun 2010 13:21:03 -0400 (EDT) Received: from artemis.silentflame.com (client-7-200.eduroam.oxuni.org.uk [192.76.7.200]) by athena.silentflame.com (Postfix) with ESMTPSA id D0E3E1AB1A5 for ; Fri, 4 Jun 2010 13:45:02 +0000 (UTC) Received: by artemis.silentflame.com (Postfix, from userid 1000) id 72338983FA; Fri, 4 Jun 2010 14:44:04 +0100 (BST) Date: Fri, 4 Jun 2010 14:44:04 +0100 From: Sean Whitton To: sup-devel@rubyforge.org Message-ID: <20100604134404.GA28767@artemis.silentflame.com> MIME-Version: 1.0 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: [sup-devel] Storing message tags and other Sup info as headers in Maildir 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="===============0634425601==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============0634425601== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" Content-Disposition: inline --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear all, I've been checking back to the Sup website every few months for the past=20 year or so, waiting until Sup starts to look more stable and suitable=20 for regular use. Like many people on this list, a great stumbling block=20 to adoption is the fact that Sup doesn't really let you access your=20 e-mail with anything other than Sup. At the moment I use offlineimap=20 and read my mail with Mutt, but my phone and SquirrelMail can access the=20 Maildir just as well (by IMAP in the former case), and so everything=20 stays in sync and I can get to my e-mail from many places. Now, I am no real coder, and I've never written a line of ruby, but a=20 thought has occurred to me that I feel I should at least share, even if=20 it turns out to be completely impractical. Why not store the=20 information associated with e-mails that is not rebuildable (that is,=20 tags, unread/read status, starred status, archived/killed/spam status)=20 as header lines (X-Sup-Tags: X-Sup-Status, and I guess read/unread could=20 be standard Maildir flags) in the e-mails themselves in the Maildir? This way, the Sup index could be rebuilt on multiple client machines=20 without any data actually going out of sync. You'll still have a=20 punishing index rebuild every time you view your mail on a new machine,=20 but they'll never be the problem of things actually being wrong - tags=20 and stars and the like can all be propagated by offlineimap/IMAP. The=20 indexer can rip out these flags into its index to maintain Sup's=20 professed speed, and then if they change, write them back into the=20 Maildir along with read/unread status and other flags. Does this exposition make sense? Is this a practical way to=20 improve/create Sup's multi-client support? S --=20 Sean Whitton / OpenPGP KeyID: 0x3B6D411B http://seanwhitton.com/ --liOOAslEiF7prFVr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJMCQMkAAoJEA9W0FU7bUEbRpIP/jB069y9wtjxgsH9Uuz/J2Z8 EhdG11Jjx5C+R3cUUNkGXzqBBo+pqCQ4PaqGUqEr6MKZX5AkhZtQWC4Unn6vOpaY 0INUICqUYDPugC1GZQYDvmn0RV8Dx2pbUGCueMGGpP2hgLPTYsObarKl5kZ5V14J nebEswm7fxP2qssUKKM2AYJF5caSyslTVLCBHDMtsZ3Br461GQ4Bd3BQwGOvl4A3 f40uKOOP8lDJ8X77XuyzK2o1VuZM0tk3Jy4el81A8AVkrGU3kdlmVvuvx0iZ4FYc Td0eWndmB7+JEwtSqEhONRObdpqGcSGUTp2YF2vifoT/JYTLVTb20Qwvf6jPwS4s T8NvWcOsZy4BlUJmHFprSDKLMsjw4ac+m2/XDGkHFUZa6+ZP7JKvzvi9+GeAfVAe pRUpdhTG+/MX0coU6SUqHng1xN74nvJCRFb6gH5pPaf8vekZmiawb/gcR/u14Wc7 SDZfLVEa2nI+w3deLsuanHu9fRnE2yH87o2R22C7tXPtTdUb80JnC7z304oorhFx n61iQzw+c26D02jpZgvL/7XIq95RTXcumt92eVSwCB4nwCJpNMf9fKIC/i7wrBz5 VIXMUsqjnpk/IGlfAb0Eh2h2HQFLiopYqzLTrIE8nRcTRAQWPSjxYnaCEZAXWJFb phVAdFuOtG7jFlBGyclq =BWMV -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- --===============0634425601== 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 --===============0634425601==--