[
https://issues.apache.org/jira/browse/MIME4J-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606758#action_12606758
]
Oleg Kalnichevski commented on MIME4J-5:
----------------------------------------
Folks,
I am currently trying to use mime4j for parsing fairly large-ish SOAP with
attachments messages. All works well as long as I am feeding mime4j with
content stream off the disk. However, mime4j fails miserably when reading
real-world content from a network socket. I _suspect_ there are issues with
parsing streams when body header gets split between several network packets.
So, I'll have to spend some time looking at the parsing logic in the
MimeTokenStream class. Simultaneously I could look into solving "byte at a
time" problem. I have experience solving similar problem for HttpCore /
HttpClient.
Essentially I would like to know
(1) whether someone is currently working on this issue,
(2) whether my attempt at solving the issue would clash with someone else's
work (MIME4J-30) and finally
(3) whether it is okay with you if I borrowed some code from HttpComponents
project and put it into mime4j?
Oleg
> Mime4j takes really long to parse big messages
> ----------------------------------------------
>
> Key: MIME4J-5
> URL: https://issues.apache.org/jira/browse/MIME4J-5
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Norman Maurer
> Assignee: Niklas Therning
> Fix For: 0.4
>
>
> From ml:
> Mime4j has general demonstrable performance problems:
> http://buni.org/bugzilla/show_bug.cgi?id=137
> http://blog.buni.org/blog/mbarker/Meldware/2007/01/27/Look-out-Its-behind-you
> I'd suggest a general code review for the "byte at a time + buffered input
> stream" anti-pattern
> and general refactoring to do things in blocks where possible.
> -Andy
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
