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
--- Begin Message ---
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
<[email protected]> 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
--- End Message ---
_______________________________________________
Ietf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf
