About Question enthuware.ocejws.v6.2.139 :

Moderators: Site Manager, fjwalraven

Post Reply
ramy6_1
Posts: 123
Joined: Wed Feb 12, 2014 2:44 am
Contact:

About Question enthuware.ocejws.v6.2.139 :

Post by ramy6_1 » Tue Nov 10, 2015 6:22 am

Hello ,

I understand that

1- using SWA The size of the SOAP attachment is more or less the same as original binary data.
The same also while using MTOM.

2- An MTOM optimized infoset+attachment for a large binary data saves around 30% in size when compared to original infoset.

So saving comes on picture if we considered XML infoset beside the SOAP attachment otherwise size will be the same.

Kindly correct me if I am wrong.

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.139 :

Post by fjwalraven » Wed Nov 11, 2015 1:56 am

Binary data in SOAP-based web services can be send in:
  1. in the SOAP body
  2. in the SOAP attachments
Add 1) the binary data will be encoded using base64 (meaning the binary data is mapped to text) and then transmitted as the payload of the SOAP body. The problem here is that the encoded version of for instance an Image is at least 33% larger then the original.

Add 2) the binary data can be transmitted (as is) in one or more attachments to a SOAP message. A SOAP attachment can carry data of any MIME type, including a MIME type as image/jpeg.

By default all binary data will be send inline!

Regards,
Frits

ramy6_1
Posts: 123
Joined: Wed Feb 12, 2014 2:44 am
Contact:

Re: About Question enthuware.ocejws.v6.2.139 :

Post by ramy6_1 » Wed Nov 11, 2015 3:10 am

Inline means data send at the soap body not attachment correct ?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.139 :

Post by fjwalraven » Wed Nov 11, 2015 8:00 am

Correct!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest