From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.218.138 with SMTP id hq10cs2701icb; Fri, 17 Dec 2010 21:52:28 -0800 (PST) Received: by 10.229.185.7 with SMTP id cm7mr1557979qcb.91.1292651547506; Fri, 17 Dec 2010 21:52:27 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id w10si1118845vbp.76.2010.12.17.21.52.27; Fri, 17 Dec 2010 21:52:27 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@jamestaylor.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E984318583AE; Sat, 18 Dec 2010 00:52:26 -0500 (EST) Received: from jamestaylor.org (jamestaylor.org [67.207.142.119]) by rubyforge.org (Postfix) with ESMTP id D6AB21858367 for ; Sat, 18 Dec 2010 00:25:05 -0500 (EST) Received: from jamestaylor.org (localhost [127.0.0.1]) by jamestaylor.org (Postfix) with ESMTP id 4A6171C181; Sat, 18 Dec 2010 05:25:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jamestaylor.org; h= content-type:cc:subject:from:to:in-reply-to:references:date :message-id:content-transfer-encoding; s=beta; bh=vd5q9UeXcNgW3G uWymF2uUS0fqA=; b=Q5S7MZ9nSe0BbIaaP/2X3hkqnx09KBSgA75cpGkjJ2w6OC pycQFSmtqY6WuPkNZjuRpAdRI0mTpnIRleireVxg8ws+/uaJKXhF9p7sDaFrZzVN FjjqodgYmxcEpjnEjzr9Qq7IKRScf85h3OlJpyqjewqrLog7dir2cdFMTLVrY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=jamestaylor.org; h=content-type :cc:subject:from:to:in-reply-to:references:date:message-id: content-transfer-encoding; q=dns; s=beta; b=aqvyyCYnfcr8vYeYTidC i+qqqv6x8XEHP8MXaAKrCnmjlrUfmeGUjQ2Fc/LokKdme7QTFbf6Ns5qFXz/V+Fs hyYYmpa0GH8lgnGXx2fkjbE6GcH4kYoi49Z4t7Se1Eft5MRlnFpDjecuG+jnX0ZA shhmkc55CKUCktq5x2+ulb0= Received: by jamestaylor.org (Postfix, from userid 1000) id 3D9311C182; Sat, 18 Dec 2010 05:25:05 +0000 (UTC) From: James Taylor To: Matthias Vallentin In-reply-to: <20101218051216.GS60419@icsi.berkeley.edu> References: <1271023429-sup-9851@zyrg.net> <1271249704-sup-1088@masanjin.net> <1271254358-sup-3024@pinkfloyd.chass.utoronto.ca> <1271260552-sup-9153@masanjin.net> <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca> <20101215081955.GF568@icsi.berkeley.edu> <1292432651-sup-6834@jamestaylor.org> <20101218051216.GS60419@icsi.berkeley.edu> Date: Sat, 18 Dec 2010 05:25:05 +0000 Message-Id: <1292649662-sup-8863@jamestaylor.org> User-Agent: Sup/git Cc: sup-talk , Ben Walton Subject: Re: [sup-talk] current state of synching upstream? 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Matthias Vallentin's message of Sat Dec 18 05:12:16 +0000 2010: > This looks like the scenario I envision. Two questions: > > - Do you use the IMAP clients as read-only clients or do you invoke > sup-sync after the devices modify the maildir (or before polling > in sup)? > > - Do you use sup-sync-back when changing message state via sup? From > what I understand, this would be desirable to copy messages from > new to cur in order to avoid a linear increase in poll times with > growing number of mails in new. Neither. The imap clients are read write, the only time this becomes a problem is when the imap client moves a message from new to cur. Sup will not be able to find the message until the next time it polls (but this is mostly seamless, if I use the imap client I just poll and refresh in sup). This does imply that sup must be polling cur as well as new. Similarly, sup-sync-back is not needed because messages are synced back to the maildir immediately. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk