[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    Fwd: iOS IMAP IDLE (Standard "Push Email") Deficiency, Explanation?
From:       Sabahattin Gucukoglu <mail () sabahattin-gucukoglu ! com>
Date:       2010-10-04 17:18:22
Message-ID: 352410DE-19D8-4EE4-8741-AB82741D7A18 () sabahattin-gucukoglu ! com
[Download RAW message or body]

Maybe my hubris got the better of me, but I didn't bargain for a =
complete surprise.  Well, anyway, we know now why Apple does not =
implement IMAP IDLE in iOS.  I've clearly been spending too much time =
around the IETF, to find Mr. Job's explanation to be completely =
incomprehensible. :-)

(Please let me know if the Message/RFC822 part didn't come through right =
- thanks.)

I want to ask anybody who feels strongly to the contrary to please not =
attack the sender (and the messenger either if you can help it :-) ).  I =
guess I'm stuck waiting 15 minutes for new mail notifications, and =
running my battery down.  I'm not forwarding my mail anywhere or running =
Exchange (or a clone).  The latter, in particular, is a power-hungry =
option ...

Cheers,
Sabahattin

["Re: iOS IMAP IDLE (Standard \" (Re: iOS IMAP IDLE (Standard \)]

Return-Path: <sjobs@apple.com>
Delivered-To: <mail-dated-1288780188.65fa7e@sabahattin-gucukoglu.com>
Received: from mail-out3.apple.com ([::ffff:17.254.13.22]:57789)
	by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server]
	id <S1FA5D> for <mail-dated-1288780188.65fa7e@sabahattin-gucukoglu.com> from \
<sjobs@apple.com>;  Mon, 4 Oct 2010 15:58:27 +0100
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55])
	by mail-out3.apple.com (Postfix) with ESMTP id E96E0AD0DE5A
	for <mail-dated-1288780188.65fa7e@sabahattin-gucukoglu.com>; Mon,  4 Oct 2010 \
                07:58:26 -0700 (PDT)
X-AuditID: 11807137-b7b43ae00000547d-67-4ca9eb925abb
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15])
	by relay16.apple.com (Apple SCV relay) with SMTP id 0A.FE.21629.29BE9AC4; Mon,  4 \
                Oct 2010 07:58:26 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.248.4.100] (wave-dhcp100.apple.com [17.248.4.100])
 by gertie.apple.com
 (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit))
 with ESMTPSA id <0L9R00H3DTLERG00@gertie.apple.com> for
 mail-dated-1288780188.65fa7e@sabahattin-gucukoglu.com; Mon,
 04 Oct 2010 07:58:26 -0700 (PDT)
Subject: Re: iOS IMAP IDLE (Standard "Push Email") Deficiency, Explanation?
References: <ABE2B6D6-6472-415D-A7FF-662CC6995C40@sabahattin-gucukoglu.com>
From: Steve Jobs <sjobs@apple.com>
X-Mailer: iPhone Mail (8B117)
In-reply-to: <ABE2B6D6-6472-415D-A7FF-662CC6995C40@sabahattin-gucukoglu.com>
Message-id: <1AC7D33F-B9B4-46E6-8B1B-D0DF0CD5E6F0@apple.com>
Date: Mon, 04 Oct 2010 07:58:15 -0700
To: Sabahattin Gucukoglu <mail-dated-1288780188.65fa7e@sabahattin-gucukoglu.com>
X-Brightmail-Tracker: AAAAAQAAAZE=

Purely technical. IMAP IDLE is a power hungry standard that is not great for mobile \
devices. 

Sent from my iPhone

On Oct 4, 2010, at 3:29 AM, Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com> \
wrote:

> If you can't tell me much, I'll understand, but please tell me at least one thing: \
> is iOS's distinctive lack of support of IMAP IDLE (and future open push standards) \
> driven mostly by business agenda, mostly by technical agenda, or both?  I know \
> Apple would hate to lower the bar for no good reason, and yet, somehow, this is the \
> situation with push email notification on iOS devices, where the open standards \
> have clear advantages.  This cannot be right, and I would love to know there was a \
> reason I've overlooked or just don't know about. 
> Confidence assured upon request.
> 
> Cheers,
> Sabahattin



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


[prev in list] [next in list] [prev in thread] [next in thread]