[
https://issues.apache.org/jira/browse/MIME4J-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654553#action_12654553
]
Markus Wiederkehr commented on MIME4J-60:
-----------------------------------------
@Oleg: In your last comment you wrote about using the strategy pattern. That
sounds a bit like option 2. I though you were in favor of option 1 yourself?
I wonder if there is even a need for a strict mode. In my opinion it would be
sufficient if Mime4j consistently considered CRLF or LF to be line breaks and
ignored isolated CRs. In other words, only a lenient mode.
I am a bit concerned about the strategy pattern in this particular case.
Wouldn't it come down to one method call per input byte?
> 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]
