Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 10460 invoked from network); 1 Dec 2009 08:32:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Dec 2009 08:32:06 -0000 Received: (qmail 42550 invoked by uid 500); 1 Dec 2009 08:32:06 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 42511 invoked by uid 500); 1 Dec 2009 08:32:06 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 42501 invoked by uid 99); 1 Dec 2009 08:32:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 08:32:06 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vdichev@gmail.com designates 209.85.219.220 as permitted sender) Received: from [209.85.219.220] (HELO mail-ew0-f220.google.com) (209.85.219.220) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 08:32:04 +0000 Received: by ewy20 with SMTP id 20so1453868ewy.20 for ; Tue, 01 Dec 2009 00:31:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=2mcR/0Wr0v0SOQg8XFiGkjKV8MAVlVUJ3k5hIVoRco0=; b=KIZP/vlTNc7iQEm93iIJ0lb5AGwzyGR9kCiSfzrD7dGu7Gg2VlUPcw4ipTeMZEac9F 7/8oHN6KgPf7CIZvDjJlVMbqqHp1PRlb457Uv4iKu/1ISEGWd33wLFbSaRY/AiWWIdiG qkldNr4ut620KCJWJbdWJEyh9OfAbc+D/BURk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=OPtlN+njnlSlwxGTkhMVgrSwrr5ZDbEWwCJ2N8c8XIqEviADMU525tP9ruGiyG7F3E TB9GnW0AQwEdz5UoMFrrdc0Jz1VxZGzrKQWzb7g25KgtDxfkoVA1bMyEfbOzzNICUvLm JJ9mSRL8l1KR6UWrmjIfL6efV5wu52s7Txj6g= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.216.89.141 with SMTP id c13mr1818103wef.66.1259656302745; Tue, 01 Dec 2009 00:31:42 -0800 (PST) In-Reply-To: <771905290912010009x2c205d83r4cb12d1d4e038a66@mail.gmail.com> References: <771905290911280012v6ded6926i4a6f4d94aa31c0ed@mail.gmail.com> <771905290912010009x2c205d83r4cb12d1d4e038a66@mail.gmail.com> Date: Tue, 1 Dec 2009 10:31:42 +0200 X-Google-Sender-Auth: ba598ef8f8a95656 Message-ID: Subject: Re: Incremental updates? From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > I thought that if we can send all messages (the last n I guess) we should > also be able to send only the last k =A0new messages in one batch. > Or is there no easy way on the server to find out which messages have not > yet seen by the client? There is, it's just that the timeline is redisplayed with only the amount of messages that are sent from the server in this batch. It should be possible to merge in with the existing list of messages, of course. As always, it's worth spending some time thinking up front whether it makes sense to do this.