james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (MIME4J-30) Transfer-encoding should be transparent
Date Thu, 20 Sep 2007 20:57:51 GMT

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

Jochen Wiedmann commented on MIME4J-30:

Robert, I do not get how this discussion escalates. If we do support "only streaming", in
combination with NIO (aka byte buffers), then we do support everything. But that's not even
the issue here. Currently, we are simply discussing my proposal to make transfer encodings
transparent. Nothing more, and nothing less.

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