MBOX-Line: From mrc+imap at panda.com  Mon Oct  4 18:18:58 2010
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc+imap@panda.com>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] Fwd: iOS IMAP IDLE (Standard "Push Email")
	Deficiency, Explanation?
In-Reply-To: <4CAA79EE.20003@aol.com>
References: <352410DE-19D8-4EE4-8741-AB82741D7A18@sabahattin-gucukoglu.com>
	<4CAA0F5C.7030009@lists.grepular.com>
	<alpine.OSX.2.00.1010041034520.392@hsinghsing.panda.com>
	<7D32DBF6-2ECC-4854-85A8-84261D828ED2@sabahattin-gucukoglu.com>
	<11166.1286223088.054596@puncture>
	<alpine.OSX.2.00.1010041338040.392@hsinghsing.panda.com>
	<4CAA7379.3070307@aol.com>
	<alpine.OSX.2.00.1010041749370.392@hsinghsing.panda.com>
	<4CAA79EE.20003@aol.com>
Message-ID: <alpine.OSX.2.00.1010041808260.392@hsinghsing.panda.com>

On Mon, 4 Oct 2010, John Snow wrote:
>> That assumes that the IMAP server notifies instantly, instead of polling
>> internally at a fixed interval.  This, in turn, assumes some form of
>> message passing between the MDA and the IMAP server.
> That's true.  I took that as am implied requirement for implementing IDLE.

There's no enforcement of such a requirement.  If IDLE is simply a
checklist requirement (which it usually is) then the simplest way to get
it checked is via an internal poll.

After all, who's gonna know?

> We live in a world full of impatient people.

How will they know?  This is a day and age when the vast majority of users
don't even have access to Received headers, much less can interpret them.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

