Re: [sup-talk] current state of synching upstream?

From: James Taylor <james@jamestaylor.org>
To: Matthias Vallentin <vallentin@icsi.berkeley.edu>
Cc: sup-talk <sup-talk@rubyforge.org>,
	Ben Walton <bwalton@artsci.utoronto.ca>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Sat, 18 Dec 2010 05:25:05 +0000	[thread overview]
Message-ID: <1292649662-sup-8863@jamestaylor.org> (raw)
In-Reply-To: <20101218051216.GS60419@icsi.berkeley.edu>

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