james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <server-...@james.apache.org>
Subject [jira] Assigned: (MIME4J-30) Transfer-encoding should be transparent
Date Tue, 23 Oct 2007 21:07:50 GMT

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

Robert Burrell Donkin reassigned MIME4J-30:

    Assignee: Jochen Wiedmann

Hi Jochen

AIUI you have karma now

IMHO the best approach would be to go ahead and apply your patches to bring the JAMES version
close to your current design. It should be discuss changes needed for the other use cases
once this has been done. I'll take up the design discussion on list.

> 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,
> 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

View raw message