Brian Candler writes:
My basic concern is that if, as in the case of Courier,Um, practically speaking, what does that mean for the client? MyBad things. RFC2060:
experience/bias with http makes me want to lower this 30 minutes
to something more like two minutes. If I could do this, what
would the user experience?
5.4. Autologout Timer
If a server has an inactivity autologout timer, that timer MUST be of
at least 30 minutes' duration. The receipt of ANY command from the
client during that interval SHOULD suffice to reset the autologout
timer.
IMAP is a remote message store which you browse interactively - and many
mails take longer to read than 2 minutes. The burden on the server of
maintaining an inactive process is minimal; the burden of doing additional
authentications and re-scanning mailboxes is not.
it is one process per user, for thirty minutes, than how many users can
your "typical 1U" web server support?
I have never used an IMAP MUA, so I have no notion of how users normally
interact with one. What happens after thirty minutes? Does the user
have to login again? That is not what happened to me today when testing
with Outlook Express and Eudora. They had my password cached (I gather)
and I was seemingly able to kill the backend processes willy nilly
without seeming to hurt anything.
So if the timeout is shortened, what might the user experience?
Thanks for your insights,
Jerry
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
