[
https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616150#action_12616150
]
Stefano Bagnara commented on MIME4J-65:
---------------------------------------
1. Can you prove this?
1b. THe current solution has bugs. We have to first fix them if we want to
compare performance, anyway.
2. I agree. Simply this one is working. THe current one not.
I've nothing against your code. I simply take care of the result: I wanted a
working solution and I wanted to propose something instead of writing useless
complaints.
Either you decide to use this or not I don't care at all.
I'm not committing code anywhere, anymore. If anyone will decide they want to
use the code I've explained that the Base64OutputStream class has been copied
from MyFace Trinidad.
> 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]
