[
https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616160#action_12616160
]
Robert Burrell Donkin commented on MIME4J-65:
---------------------------------------------
Using streams and copying introduces multiple buffering but I don't want to
argue. You prefer another design approach which is fine. Just go ahead and
commit your proposal. As you have probably worked out, I don't really care
about the DOM API. I definitely don't care enough to waste so much time arguing
about it. The performance is probably not critical.
Please don't get so upset. You've done some good work over the last week or so
but you need to learn to bring the community with you when you push. I thought
that we'd all started to work together towards fixing things earlier this week.
Unfortunately that seems not to be the case.
Robert
> Message.writeTo for an rfc822 part ignoring a "base64" encoding
> ---------------------------------------------------------------
>
> Key: MIME4J-65
> URL: https://issues.apache.org/jira/browse/MIME4J-65
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4, 0.5
>
> Attachments: MIME4J-65-complete.patch, MIME4J-65.patch,
> testmsgs-message-rfc822-encoding.zip
>
>
> the writeTo method for a Content-Transfer-Encoding: base64 and Content-Type:
> message/rfc822 part writes the message unencoded.
> I would expect it to be encoded in a base64 stream. See MIME4J-64 for an
> useful test.
--
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]
