Re: Committing patch contributed for MIME message parser and serializer based on Apache mime4j [WSCOMMONS-387]

Hi Dims

I am not clear on this.. what you are suggesting is to just move the new 
code to another maven module only? or to make it available as an option 
to someone who wants to use it? If the new implementation has drawbacks 
I understand, but if its better, why not just switch? or are we looking 
for more performance test results to decide on this?

asankha
> On Tue, 2008-11-18 at 22:50 -0500, Davanum Srinivas wrote:
>   
>> Asankha,
>>
>> Please check in ONLY if the new MIME4J dependent code is in another
>> maven module.
>>
>> thanks,
>> dims
>>
>>     
>
> Asankha et al
>
> The patch was meant as a replacement for the existing implementation. It
> is pointless to have two MIME frameworks in Axiom. Just forget about the
> patch.
>
> Oleg
>
>
>   
>> On Tue, Nov 18, 2008 at 9:46 PM, Asankha C. Perera <[email protected]> wrote:
>>     
>>> Hi all
>>>
>>> Last night I noticed that the patch contributed by Oleg for better MIME
>>> parsing [1] has not yet been committed after 2 months
>>>
>>> The patch is still valid against the trunk, but I am not in the best
>>> position to analyze it at an Axiom level, but I am very confident of its
>>> benefits, and thus would like to request someone more capable to review it
>>> ASAP, failing which I will commit it shortly
>>>
>>> thanks
>>> asankha
>>>
>>> [1] https://issues.apache.org/jira/browse/WSCOMMONS-387
>>>
>>> "Mime4j can handle very complex MIME messages, is reasonably fast, and, most
>>> importantly, can stream complex MIME messages in and out with a predictable
>>> memory footprint (using just a small internal buffer of a constant length).
>>> This patch expects to allow Axiom to provide an alternative API based on a
>>> fully streamable model."
>>>       
>   


-- 
Asankha C. Perera
http://adroitlogic.org

http://esbmagic.blogspot.com