[
https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617132#action_12617132
]
Robert Burrell Donkin commented on MIME4J-65:
---------------------------------------------
Re: Encoding
Sorry for being unclear
In theory, a single stage that copies and encodes should be more performant
that a two separate stages (copy then encode). The tradeoff is that single
stage implementations are more difficult to write and maintain.
Personally speaking, I would find the single stage easier. But if you can't
easily understand the algorithm then there's not much hope for anyone else. So
I don't think it unreasonable to go for a more mature but less performant
solution in this case. The current implementation is not mature but could be
fixed. If you prefer the single stage approach, I'll find some time to fix it.
If not, then that's fine.
> 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]
