[
https://issues.apache.org/jira/browse/MIME4J-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995542#comment-12995542
]
Rohan Hart edited comment on MIME4J-164 at 2/16/11 10:07 PM:
-------------------------------------------------------------
Hi Oleg
Fill the buffer and parse as much as possible. Take what remains and fill the
rest of the buffer with as much of the remaining address field as will fit.
Parse and repeat.
I did have a subsequent email conversation with Stefano (see
http://www.mail-archive.com/[email protected]/msg00878.html ) where
it seemed that the best option was to make fields in general have a String
header and InputStream (rather than fixed buffer) body.
thanks
Rohan
was (Author: rohan.hart):
Hi Oleg
Fill the buffer and parse as much as possible. Take what remains and fill the
rest of the buffer with as much of the remaining address field as will fit.
Parse and repeat.
I did have a subsequent email conversation with Stefano (see
http://www.mail-archive.com/[email protected]/msg00878.html) where it
seemed that the best option was to make fields in general have a String header
and InputStream (rather than fixed buffer) body.
thanks
Rohan
> Incremental address list field parsing
> --------------------------------------
>
> Key: MIME4J-164
> URL: https://issues.apache.org/jira/browse/MIME4J-164
> Project: JAMES Mime4j
> Issue Type: Improvement
> Affects Versions: 0.6
> Environment: Java 6
> Reporter: Rohan Hart
> Priority: Minor
> Fix For: 0.7
>
>
> To avoid buffer limits it would be good for address list field parsing to
> interleave reading the stream with parsing individual addresses.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
