[
https://issues.apache.org/jira/browse/MIME4J-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655686#action_12655686
]
Oleg Kalnichevski commented on MIME4J-60:
-----------------------------------------
@Markus: I am currently leaning towards option 2. The reason being I would like
to try to fix this issue once and for all. I also do not think the strict mode
is useful, but at the very least one could have an option of making sure that a
lone CR would cause a MimeException, since this problem happened to be such a
major point of contention.
> Wouldn't it come down to one method call per input byte?
As long as data is not read one byte at a time from the input stream I do not
think there is going to be any noticeable performance penalty. I'll run some
basic benchmarks to be really sure, though.
I am a bit busy trying get HttpClient 4.0b2 released soon. If circumstances
permit I should have more time for mime4j sometime next week.
Cheers
Oleg
> Configurable strategy for line delimiters
> -----------------------------------------
>
> Key: MIME4J-60
> URL: https://issues.apache.org/jira/browse/MIME4J-60
> Project: JAMES Mime4j
> Issue Type: Wish
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.6
>
> 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]
