[
https://issues.apache.org/jira/browse/MIME4J-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616182#action_12616182
]
Robert Burrell Donkin commented on MIME4J-60:
---------------------------------------------
Thanks for clearing up the confusion: this is about parsing headers ending in CR
By "cost of support" I mean the cost that adding this ertra feature will cost.
MIME4J-60-readLine-returns-no-newline.patch will degrade performance (by
introducing extra copy, search and conditional operations into a loop) and add
complexity. Whether this degradation is important in practice, I don't know.
What I like about this patch is that it's very clean. It might be possible to
give a user the choice between between performance and support for CRs
> Configurable strategy for line delimiters
> -----------------------------------------
>
> Key: MIME4J-60
> URL: https://issues.apache.org/jira/browse/MIME4J-60
> Project: Mime4j
> Issue Type: Wish
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.5
>
> Attachments: MIME4J-60-readLine-returns-no-newline.patch,
> newlines-tests.zip, newlinestrat.patch
>
>
> There is an ongoing discussion about how we should deal with non canonical
> line endings (isolated LF and/or isolated CR).
> This issue is to track discussion results and proposed patches.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
