> > > if I (as an IMAP client) have to exit quickly and have an open IMAP > > > connection, I can't wait around for the IMAP server's responses. > > > > What is the reason for this ? > > I can think of four possible reasons right away. There might be more. > > 1. The user closes the MUA's window.
I don't see why you wouldn't send the close when the user closes the MUA window. Remember that in a GUI, protocol and user interface implementations should not be linked too much. > 2. The user logs out, and the session manager tells applications to save > their state and exit quickly. the session manager have to wait for the application to exit. > 3. The application is told that the machine will suspend in 0.1 seconds (a > laptop, typically). then, the application will be interrupted. > 4. The application runs on unix and receives e.g. SIGINT. in this case, anything will be broken, at least the IMAP session. > > You have at least to wait for the IMAP response of the command you > > want to send. > > Sorry, no can do. For example, when you request a FETCH, you have to wait for the response. If you can wait for the fetch, I think that you can wait for the logout which may be almost immediate. > If I have to choose, I'd rather write a good application than a good IMAP > client. respect the specifications is a good point to reach the status of "good application". -- DINH V. Hoa, libEtPan! - a mail library - http://libetpan.sourceforge.net "sunZ ! capitaine de soir�es"
