[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 7765] Online/offline
From:       matt () eisgr ! com
Date:       2005-01-10 14:48:33
Message-ID: 20050110144833.32455.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
        
http://bugs.kde.org/show_bug.cgi?id=7765        




------- Additional Comments From matt eisgr com  2005-01-10 15:48 -------
Agree with Carston.

Offline in this thread seems to have two meanings:
*) Can't reach the network:
This basically means that the client gracefully sits idle instead of CPU-hogging \
(like Thunderbird sometimes does) trying to reconnect.  This can be resolved cleanly \
by a simple IMAP/POP3-ping so-to-speak.  Every <insert favorite timing interval here> \
seconds a thread wakes up and checks the availability of the default mail server.  \
TCP Connect or possibly even ping (configurable) should prove sufficient.  It also \
strikes me that it is most valuable to check the default gateway's availability, with \
slightly more value checking the server.  Just my $0.02

*) Offline mode, including the above definition, but pre-emptive offline (ie.  We \
tell it to go offline *before* the network goes away).  This then includes  (ok, this \
is actually the most value anyway) downloading email to offline IMAP folders.  This \
of course infers that we must be able to flag IMAP folders for offline use.  As Marco \
(and others) have already mentioned, this is one of the primary values to Offline \
Mode.  Who cares if I have to close KMail if I'm not able to use it? \
_______________________________________________ KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]