[
https://issues.apache.org/jira/browse/MIME4J-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616195#action_12616195
]
Robert Burrell Donkin commented on MIME4J-67:
---------------------------------------------
Please just go ahead and commit your solution. I'm happy to trade some
performance for code that it's easier for others to maintain providing that
this tradeoff is understood.
One of the reasons why I felf so frustrated is that you're so close to being
really good at this but you just start pushing a little faster than the
community is comfortable with and then don't manage the inevitable reaction
very well. Part of it is practice. Getting annoyed and walking away doesn't
help anyone. Please give it another go :-)
Another reason why I feel so frustrated is that I had a definite feeling that
JAMES community was turning the corner. I have been very busy and unwell over
the last few weeks. I made mistakes.
Robert
> Base64Encoder fails to encode streams longer than its buffer size (1024)
> ------------------------------------------------------------------------
>
> Key: MIME4J-67
> URL: https://issues.apache.org/jira/browse/MIME4J-67
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4
>
>
> When encoding streams longer than 1024 bytes the encoder simply concatenate
> the base64 version of each 1024 chunk and this is wrong. Base64 streams are
> only concatenable when the original text length was a multiple of 3.
> Supporting buffer chunks encoding require keeping the last 1-2 bytes in a
> buffer and eventually convert them to base64 ending sequences only when the
> stream is closed.
--
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]
