[
https://issues.apache.org/jira/browse/MIME4J-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671456#action_12671456
]
Markus Wiederkehr commented on MIME4J-114:
------------------------------------------
Retrieving the byte offset from the underlying input stream might be tricky
since Mime4j uses a few buffers when parsing a message. I'm not saying it is
impossible of course.
Inner transfer encodings are something else to consider. Let's say you had a
message that contains another (maybe forwarded) message in base64 encoded form.
That inner message can of course also have parts that are transfer encoded
themselves. A byte offset alone does not help with retrieving parts of the
inner message.
> Efficient Read Access To Parts Of A Parsed Document
> ---------------------------------------------------
>
> Key: MIME4J-114
> URL: https://issues.apache.org/jira/browse/MIME4J-114
> Project: JAMES Mime4j
> Issue Type: Wish
> Affects Versions: 0.6
> Reporter: Robert Burrell Donkin
> Fix For: 0.7
>
>
> Use Case
> --------------
> Consider a large MIME document stored (as a single document) in a medium
> which allows random access to the bits (for example, a BLOB in a data store
> or a file.)
> I parse the document once using Mime4J and store the meta-data (for example,
> in a data store) so that I can read this data many times without loading and
> reparsing this large document
> I wish to be able to read efficiently a part of the document without loading
> the whole, and this may happen frequently
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
