[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 82805] connection suddenly broken with imap
From: David Faure <faure () kde ! org>
Date: 2004-06-04 9:33:07
Message-ID: 20040604093307.13137.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=82805
faure kde org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
------- Additional Comments From faure kde org 2004-06-04 11:33 -------
On Friday 04 June 2004 11:24, Andreas Gungl wrote:
> This problem was fixed in CVS about one or two days after it's appearance. Perhaps \
> the alpha release just hit that bug.
Was it? I have my doubts.
The timer that regularly sends NOOP to the slave to prevent a timeout,
still isn't re-enabled for online-imap.
imapaccountbase.cpp: connect(&mIdleTimer, SIGNAL(timeout()), \
SLOT(slotIdleTimeout()));
imapaccountbase.cpp: mIdleTimer.stop();
imapaccountbase.cpp: mIdleTimer.stop();
imapaccountbase.h: QTimer mIdleTimer;
kmacctcachedimap.cpp: mIdleTimer.stop();
kmacctcachedimap.cpp: mIdleTimer.start( 60000 ); // send a noop every minute to \
avoid "connection broken" errors
kmacctimap.cpp: mIdleTimer.stop();
I added the kmacctcachedimap one, to fix this bug for cached imap,
but someone should start/stop the idletimer for online imap.
If it's too complex to find out when online imap is busy and when it's idle
[imho it would need a refcount instead of a bool], I think it would be simpler to
just fire the timer in the constructor and let kmail send a noop every minute or so.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic