When a SOAP envelope is optimized on the wire, the following can be said about the optimized infoset : (Choose one)
A.
optimized infoset contains xop:Include elements with href attribute pointing to attachment data
B.
optimized infoset contains mtom:Import with location attribute pointing to attachment data
C.
optimized infoset doesn’t have any specific elements for MIME attachment.
D.
optimzed infoset’s element contain cid:Content-ID as the text and Content-ID refers to the associated attachment
A
A
XOP allows the binary data part of an XML Infoset to be serialized without going through the XML serializer. The XML serialization of an XML Infoset is text based, so any binary data will need to be encoded using base64. Using XOP avoids this by extracting the binary data out of the XML Infoset so that the XML Infoset does not contain binary data and the binary data can be serialized differently.
Therefore, XOP can reduce the size of the serialization (since base64 encoding has approximately a 33% size overhead) and (depending on how it is implemented) might allow processing efficiencies. This size increase results in extra resources needed to transmit or store the data.
MIME-Version: 1.0
Content-Type: Multipart/Related;boundary=MIME_boundary;
…
–MIME_boundary
Content-Type: application/xop+xml;
…
<soap:Envelope …
<soap:Body …
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include"
href="cid:http://example.org/me.png" m:photo
…
–MIME_boundary
Content-Type: image/png
Content-Transfer-Encoding: binary
Content-ID:
// binary octets for png
https://en.wikipedia.org/wiki/XML-binary_Optimized_Packaging