MTOM vs SWA vs Base64Binary


J2EE patterns: MTOM vs SWA vs Base64Binary

  1. MTOM vs SWA vs Base64Binary (1 messages)

    MTOM provides an elegant and simple way of transmitting attachments by converting Base64Binary encoded data into Binary MIME data over the wire. MTOM has the following advantage over SOAP with Attachments: - MTOM leverages existing standards for securing information such as WS-Encryption and WS-Signatures without requiring specialized standards for securing attachments. Developers are oblivious to the binary conversion of their Base64 data. The conversion takes place right before data transmission on the wire. MTOM has the following advantage over transmitting Base64Binary encoded data: - Base64Binary encoded data bloats the attachment by ~33%. MTOM converts the Base64Binary data to raw bytes over MIME, thus reducing the wire foot-print for transmission. The reciever can optinally convert the raw bytes back to Base64Binary encoding. For a detailed hands-on introduction to MTOM and its advantages, the following article is useful: Introduction to MTOM: A Hands-on Approach
  2. Re: MTOM vs SWA vs Base64Binary[ Go to top ]

    Good info, except it would have been helpful if the example was a Java instead of .NET