james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Resolved] (MIME4J-166) incremental structured field parsing when buffer limits reached
Date Wed, 06 Apr 2011 16:59:05 GMT

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

Oleg Kalnichevski resolved MIME4J-166.

    Resolution: Fixed


I added a more lenient implementation of FieldBuilder which unlike the default one quietly
truncates MIME fields exceeding the max limit. 

Please have a look.

LenientFieldBuilder should also be more resource efficient compared to DefaultFieldBuilder
as it does not maintain original raw content and generates less intermediate garbage on heap.


> incremental structured field parsing when buffer limits reached
> ---------------------------------------------------------------
>                 Key: MIME4J-166
>                 URL: https://issues.apache.org/jira/browse/MIME4J-166
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Rohan Hart
>            Assignee: Oleg Kalnichevski
>            Priority: Minor
>             Fix For: 0.7
> Building on MIME4J-164 and MIME4J-165 it would be good to allow structured fields, such
as address lists, to optionally recover from Max Line Limit issues by extracting what it can
and moving to the next part of the structured field, if any.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message