[
https://issues.apache.org/jira/browse/IMAP-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning updated IMAP-246:
---------------------------------
Priority: Minor (was: Major)
Fix Version/s: (was: 0.2)
Issue Type: Improvement (was: Bug)
You are correct. This is not something which is required by the RFC. I think it
would be nice to be able to use a short default read timeout and then a longer
IDLE read timeout but I'm ok with postponing this one. Also it's not really a
bug and it's not very important so I'll update Issue Type and Priority.
What do you think? Or should we just close it?
> Use different read timeout when in IDLE
> ---------------------------------------
>
> Key: IMAP-246
> URL: https://issues.apache.org/jira/browse/IMAP-246
> Project: JAMES Imap
> Issue Type: Improvement
> Components: Protocol
> Reporter: Niklas Therning
> Assignee: Niklas Therning
> Priority: Minor
>
> If the client doesn't send anything within the configured read timeout the
> connection will be closed. During IDLE I think there should be another
> timeout which is typically configured to be a lot higher than the ordinary
> read timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
