On Thu, 6 May 2010, Timo Sirainen wrote:
Instead of fighting clients with this, I solved it by having server send * OK Hang in there.. about every 15 seconds during long running commands. Clients seem to be happy with it and not disconnect.
Unfortunately, the mobile device guys and gals then get unhappy with you for chewing up their battery. It's not as bad as making them transmit, but it still causes a wakeup. They aren't placated when you tell them that it's to work around stupid clients. They get unhappy even with an untagged OK every two minutes during IDLE to quell a NAT timeout. As well they should be. The problem with going down the path of kludges and workarounds for broken entities is that it's a never-ending process. You are faced both with something else that is even more broken, and some innocent party that was fine until you broke it with your workaround. -- 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. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
