Re: [Dovecot] Feature Request: Control over IMP IDLE 'OK Still Here' message timings

2009-04-18 Thread Stian Jordet 
Robert Goldsmith skrev:

[...]

 Therefore, can you please make the timeout changeable from the config
 file, even if it defaults to the current 2min timing, so admins
 supporting mobile users can balance battery life with a need to
 prevent killed tcp connections. 

I'm amazed how you figured this out. I just thought my phone used more
battery when connected to IMAP, I never thought it had anything to do
with the OK Still Here messages (altough I knew they existed).

Thanks for letting us all know, and thanks to Timo for accepting
Robert's patch!

Regards,
Stian

[Dovecot] Feature Request: Control over IMP IDLE 'OK Still Here' message timings

2009-04-04 Thread Robert Goldsmith 

Hi all,

I would like to make a feature request regarding IMAP Idle support.

Currently when a client triggers Idle support, Dovecot then sends 'OK  
Still Here' messages every 2 minutes. This is apparently to prevent  
NAT systems killing the tcp connection and disconnecting the client.  
However, while this may be fine for desktop clients, this rapidly  
drains the battery life of mobile clients such as phones.  
Unfortunately, the timing control on this behaviour is a c define at  
the top of cmd-idle.c and is only adjustable at compile-time. I have  
experimented with this define and find a timeout of 20 minutes between  
'OK' messages is perfectly adequate for my system setup and results in  
a significant battery saving for my Nokia 6120c (increasing from ~ 6  
hours to ~ 55 hours from full charge to low battery warning).


Therefore, can you please make the timeout changeable from the config  
file, even if it defaults to the current 2min timing, so admins  
supporting mobile users can balance battery life with a need to  
prevent killed tcp connections.


Thanks

Robert Goldsmith
---
GnuPG public key:
http://www.Far-Blue.co.uk




PGP.sig
Description: This is a digitally signed message part