Re: iOS IMAP IDLE (Standard "Push Email") Deficiency, Explanation?
Eric Burger <eburger@standardstrack.com> Wed, 06 October 2010 00:39 UTC
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6DED3A70AF for <ietf@core3.amsl.com>; Tue, 5 Oct 2010 17:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XE6+lnlvttk for <ietf@core3.amsl.com>; Tue, 5 Oct 2010 17:38:55 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.249.249]) by core3.amsl.com (Postfix) with ESMTP id CCB063A70AC for <ietf@ietf.org>; Tue, 5 Oct 2010 17:38:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=cEKMzc0i6fKw7b1lYoVonSHlypebAJzras2uP866lI2u3qjGqzv5mIl5Cw5kx8+BJPtHAoyhaen86TTfaII1vpLgPLPZZ0/vl0p+8HrVgVDN5YWiFeX2ny+A0Xiq/+dk;
Received: from [38.110.19.75] by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1P3I2o-0002xe-62; Tue, 05 Oct 2010 17:39:42 -0700
Subject: Re: iOS IMAP IDLE (Standard "Push Email") Deficiency, Explanation?
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="iso-8859-1"
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <201010051513.35217.martin.konold@erfrakon.de>
Date: Tue, 05 Oct 2010 20:39:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <23DEAD4B-BC76-4812-926A-36C368150DE9@standardstrack.com>
References: <352410DE-19D8-4EE4-8741-AB82741D7A18@sabahattin-gucukoglu.com> <201010051513.35217.martin.konold@erfrakon.de>
To: Martin Konold <martin.konold@erfrakon.de>
X-Mailer: Apple Mail (2.1081)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 00:39:01 -0000
LEMONADE is beyond finished. What is to wait for? On Oct 5, 2010, at 9:13 AM, Martin Konold wrote: > Am Montag 04 Oktober 2010, 19:18:22 schrieb Sabahattin Gucukoglu: > > Hi, > > Well, Steve Jobs is partly correct. (I avoided bothering him with my > response) > > On one hand IMAP IDLE has absolute minimal requirements with regards to > protocol complexity which helps preserving power. > > On the other hand IMAP IDLE is so limited in features that it has also > negative effects on resource usage including user experience and power > consumption. > > 1. IMAP IDLE can only monitor a single folder. Using multiple connections in > order to circumvent this limitation is inefficient. > > -->3 years ago I drafted an RFC which tries to solve this issue while > remaining simple. > > http://www.erfrakon.de/konold/draft-konold-imap-idleplus-05.txt > > 2. IMAP IDLE lacks support for non mail folders e.g. clients are interested in > watching calendars, addressbooks, todos etc. > > --> I tired successfully with warpping these groupware related objects as XML > objects within imap messages (Kolab architecture) > > http://kolab.org/doc/concept-draft-cvs20060921.pdf > > 3. IMAP IDLE requires a permanent stateful TCP connection and has no support > for efficient reconnects. This means that clients cannot switch off the IP > stack in order to preserve power and that loss of connection leads to extra > bandwidth and processing requirements. This is not only bad for mobile > clients. > > All the above issues are tried to be addressed by the LEMONADE group e.g. > IMAP CONDSTORE. > > http://www.lemonadeformobiles.com/quick.html and > http://datatracker.ietf.org/wg/lemonade/charter/ > > I am personally not really happy about the technical approach and progress > sofar but I have been told by others who know much better than me to stop my > above efforts and wait patiently for the results of the LEMONADE group. > > Yours, > -- martin > > -- > e r f r a k o n > Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker > Sitz: Adolfstraße 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126 > http://www.erfrakon.com/ > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf
- Fwd: iOS IMAP IDLE (Standard "Push Email") Defici… Sabahattin Gucukoglu
- Re: Fwd: iOS IMAP IDLE (Standard "Push Email") De… Martin Konold
- Re: iOS IMAP IDLE (Standard "Push Email") Deficie… Eric Burger