From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from [192.168.1.207] (c4C8F5BC1.dhcp.as2116.net. [193.91.143.76])
        by mx.google.com with ESMTPSA id n3sm24811431lag.9.2013.07.29.12.49.11
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 29 Jul 2013 12:49:12 -0700 (PDT)
Message-ID: <51F6C6FE.1090604@gaute.vetsj.com>
Date: Mon, 29 Jul 2013 21:48:14 +0200
From: Gaute Hope <eg@gaute.vetsj.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sup developer discussion <sup-devel@rubyforge.org>
CC: Horacio Sanson <hsanson@gmail.com>
Subject: Re: [sup-devel] Gmail source sync back.
References: <CAHWBo_bRwKArh7nLQ8EMWdWvBV_kRGT=NqDU=Z69pTY+fNpMUQ@mail.gmail.com>
In-Reply-To: <CAHWBo_bRwKArh7nLQ8EMWdWvBV_kRGT=NqDU=Z69pTY+fNpMUQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 03. juli 2013 11:44, Horacio Sanson wrote:
> - Sync back iterates over all messages in the Gmail account checking for
> differences between message labels. This can take a long time and may not
> finish before the next polling starts. How to do this efficiently?

By the way, with the source poll locking recently added no second poll
should be able to be initiated when there is one running already.

- gaute