MBOX-Line: From tss at iki.fi  Mon Oct  4 18:17:01 2010
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] Fwd: iOS IMAP IDLE (Standard "Push Email")
	Deficiency, Explanation?
In-Reply-To: <alpine.OSX.2.00.1010041759160.392@hsinghsing.panda.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>
	<11166.1286226226.318772@puncture>
	<alpine.OSX.2.00.1010041405460.392@hsinghsing.panda.com>
	<959754EE-4A2A-4DBD-8A63-6A317532C302@iki.fi>
	<alpine.OSX.2.00.1010041759160.392@hsinghsing.panda.com>
Message-ID: <07A4B2F1-7841-4BCE-B82B-A82B7D14AB10@iki.fi>

On 5.10.2010, at 2.08, Mark Crispin wrote:

> On Tue, 5 Oct 2010, Timo Sirainen wrote:
>> So nowadays
>> my server never disconnects clients on IDLE because they haven't sent
>> anything. That fixes the whole thing. I still send "* OK Still here"
>> events every 2 minutes, so connections that are actually gone will get
>> disconnected pretty quickly.
> 
> Be careful.  If you don't get a disconnect event, you'll presently end up
> filling the TCP window and then block.

Luckily I don't do any blocking reads or writes.

>> This doesn't help clients that use one IDLEing connection that does
>> nothing but IDLE, and use another connection for actually fetching the
>> new mails.
> 
> Clients actually do this?  Deep sigh.  Doesn't anyone have a clue as to
> how to write software any more?  Or "if it ain't in the Java cookbook, it
> can't be done"???

I remember when I first heard of this it was a plugin (or something) that simply woke up Mail.app, because it didn't support IDLE itself. Nowadays Mail.app supports IDLE, so this plugin is no longer used. But I can't remember if that was the only problematic case.
