axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Madhav <rrmad...@gmail.com>
Subject Re: [Axis2] message transmission optimization
Date Thu, 17 Jul 2008 16:30:15 GMT
Hi Stefan,

Yes, I meant the same thing - ASCII characters (like String literals)
ultimately encoded as base64.

Samisa,

Did you mean the same thing which Stefan has mentioned or something else?

Thanks,
Madhav

On Thu, Jul 17, 2008 at 9:00 PM, Chefo <cheffo@gmail.com> wrote:

> Hi,
>
> what do you mean by ASCII text content? Ascii encoded text file?
> If so, in axis2 you have two options - either send it as base64 in the
> message (where each base64 character obviously represents 6 bits) or send as
> a separate mime part (that would be the mtom) as binary. The latter one will
> be obviously more efficient in terms of message size since even with ascii-7
> each char is 7 bits. If compared to axis1 I'd guess it would be nearly the
> same as a soap attachment - the only benefit you get is that it is more
> convenient to work with the mtom than the swa...
>
> Regards,
> Stefan
>
>
> On Thu, Jul 17, 2008 at 4:26 PM, Madhav <rrmadhav@gmail.com> wrote:
>
>> Hi,
>>
>> In Axis2, MTOM enables a more efficient transmission for binary content.
>> Is Axis2 more optimized for sending even a ASCII text content than Axis1 ?
>>
>> Thanks,
>> -Madhav
>>
>
>


-- 
-Madhav

Mime
View raw message