Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Matthias Vallentin <vallentin@ICSI.Berkeley.EDU>
To: James Taylor <james@jamestaylor.org>
Cc: sup-talk <sup-talk@rubyforge.org>,
	Ben Walton <bwalton@artsci.utoronto.ca>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Fri, 17 Dec 2010 21:12:16 -0800	[thread overview]
Message-ID: <20101218051216.GS60419@icsi.berkeley.edu> (raw)
In-Reply-To: <1292432651-sup-6834@jamestaylor.org>

On Wed, Dec 15, 2010 at 05:06:54PM +0000, James Taylor wrote:
> For what it is worth, I've been using maildir-sync for almost six months
> every day, no problems. I exercise it pretty hard since I usually have
> at least four imap clients (mobile devices and such) accessing the
> maildir simultaneously via dovecot imap. 

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.

   Matthias
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-12-18  5:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  9:40 Ryan Barrett
2010-04-11 17:52 ` Ryan Barrett
2010-04-12  0:57 ` Rich Lane
2010-04-12  5:02   ` Andrew Pimlott
2010-04-12 12:11     ` Daemian Mack
2010-04-12  9:53   ` Tero Tilus
2010-04-14 13:00   ` William Morgan
2010-04-14 14:16     ` Ben Walton
2010-04-14 15:57       ` William Morgan
2010-04-14 16:08         ` Ben Walton
2010-12-15  8:19           ` Matthias Vallentin
2010-12-15 17:06             ` James Taylor
2010-12-18  5:12               ` Matthias Vallentin [this message]
2010-12-18  5:25                 ` James Taylor
2010-12-18 19:04                   ` Matthias Vallentin
2010-12-18 19:21                     ` Ben Walton
2010-12-18 20:02                       ` Tero Tilus
2010-12-18 20:12                         ` Ben Walton
2010-12-21  6:44                       ` Matthias Vallentin
2010-12-21  6:48                         ` Matthias Vallentin
2010-12-21 11:01                         ` Tero Tilus
2010-12-21 14:11                           ` Ben Walton
2010-12-22 14:42                             ` Matthias Vallentin
2010-12-22 16:27                               ` Tero Tilus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101218051216.GS60419@icsi.berkeley.edu \
    --to=vallentin@icsi.berkeley.edu \
    --cc=bwalton@artsci.utoronto.ca \
    --cc=james@jamestaylor.org \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox