[ http://issues.apache.org/jira/browse/JAMES-700?page=all ]
Robert Burrell Donkin updated JAMES-700:
----------------------------------------
Attachment: james-imap-client-unstable.patch
Just FYI
this was my first attempt I had at resolving this issue. it didn't work very
well. basically it catchs all runtimes at the handler level. i found it better
to resolve this at a lower level (see later). this code is still in my local
fork.
IMHO the factoring out is an improvement: it improves diagnostics and
readability but the semantics are incorrect (for the reasons you outlined
above).
> James resets connection when command throws RuntimeException
> ------------------------------------------------------------
>
> Key: JAMES-700
> URL: http://issues.apache.org/jira/browse/JAMES-700
> Project: James
> Issue Type: Improvement
> Components: IMAPServer
> Reporter: Robert Burrell Donkin
> Fix For: Trunk
>
> Attachments: james-imap-client-unstable.patch
>
>
> I think that whenever a exception is thrown when processing an IMAP command
> the socket connection is reset. This behaviour seems little less polite than
> it needs to be. IMAP is stateless and IMHO errors should be returned within
> the band.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
