[jira] Updated: (MIME4J-30) Transfer-encoding should be transparent

["Oleg Kalnichevski (JIRA)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/MIME4J-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski updated MIME4J-30:
------------------------------------

    Attachment: mime4j.patch

A lightly different take than Jochen's. The main difference is that I left automatic content decoding optional.

Please review.

Oleg

> Transfer-encoding should be transparent
> ---------------------------------------
>
>                 Key: MIME4J-30
>                 URL: https://issues.apache.org/jira/browse/MIME4J-30
>             Project: Mime4j
>          Issue Type: Improvement
>    Affects Versions: 0.3
>            Reporter: Jochen Wiedmann
>            Assignee: Jochen Wiedmann
>             Fix For: 0.4
>
>         Attachments: mime4j-transfer-encoding.patch, mime4j-transfer-encoding.patch, mime4j-transfer-encoding.patch, mime4j.patch
>
>
> Currently the mime4j user must be aware of the transfer-encoding header.
> a) This is inconvenient. I can think of no reason, why a user should want the encoded data stream.
> b) This blocks MIME4J-27 in the following sense: If a user configures a limit on the attachments size,
>      then this should most possibly limit the decoded attachments size. But Mime4j can only track
>      the decoded attachments size, if it is itself responsible for decoding.

-- 
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org