axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksander Slominski <as...@cs.indiana.edu>
Subject Re: [Axis2] - OM and MTOM
Date Thu, 28 Oct 2004 05:44:39 GMT
Srinath Perera wrote:

>I think our problem is when we build he OM we do not know the content
>of a element is binary data and it will converted to the string. If we
>chaeck for that by looking at the attributes then we compromize the
>performance. thoughts ?
>  
>
Srinath,

what are exactly your performance concerns?

i think that there is no much of choice: MTOM pre-handling must happen 
during XML parsing/streaming this way it is optimal for performance and 
happens during building of OM.

thanks,

alek

>
>On Thu, 28 Oct 2004 10:52:08 +0600, Eran Chinthaka
><chintaka@opensource.lk> wrote:
>  
>
>> 
>> 
>>
>>Can we introduce a OMBinaryNode to OM to represent the base64 which are MTOM
>>compliant. 
>>
>>  
>>
>>But I have a problem of identifying optimized and un-optimized data in the
>>parser level. Can we represent everything as Strings, whether optimized or
>>unoptimized. The Element having the base64 data *may* have some information
>>in its attributes to identify. But do we have to check all the elements for
>>this, and what if the element do not have those info, but contains base64
>>data. 
>>
>>  
>>
>>Thoughts & Comments …… ?? 
>>
>>  
>> ________________________________
>> 
>>
>>Eran Chinthaka 
>>
>>Lanka Software Foundation 
>>
>>
>>    
>>
>
>  
>


-- 
The best way to predict the future is to invent it - Alan Kay


Mime
View raw message