Message Transmission Optimization Mechanism
MTOM is the W3C Message Transmission Optimization Mechanism, a method of efficiently sending binary data to and from Web services.
MTOM is usually used with the XOP (XML-binary Optimized Packaging).
Application
[edit]MTOM only optimizes element content that is in the canonical lexical representation of the xs:base64Binary data type. Since there is no standard way to indicate whether data is in the canonical lexical representation, the mechanism for applying MTOM is implementation-dependent.
The use of MTOM is a hop-by-hop contract between one SOAP node and the next. There is no guarantee that the optimization will be preserved if there are multiple SOAP nodes involved.
Details
[edit]Although most users treat MTOM as a single mechanism, the MTOM specification defines it as three related features:
- Firstly, an "Abstract SOAP Transmission Optimization Feature" for sending and receiving SOAP messages that contain binary data. The binary data is a part of the single XML Infoset model, but this feature introduces the concept of sending the binary data separately (i.e. not in the serialized XML infoset).[1] This abstract feature does not define how the serialized XML infoset looks without the binary data, nor how the binary data is actually represented.[2]
- Secondly, an "Optimized MIME Multipart/Related Serialization of SOAP Messages" is defined. This defines that the serialized XML infoset will include XML-binary Optimized Packaging (XOP) in place of the binary data, and the binary data (along with the serialized XML infoset with XOP placeholders) will be represented together in a MIME container.[3] Although this defines a SOAP message, it does not define the transport protocol over which that MIME and XOP SOAP message is sent.
- Thirdly, a "HTTP SOAP Transmission Optimization Feature" defines how the above MIME and XOP SOAP message is sent over HTTP.
Sometimes the term "MTOM" is used as a shorthand to mean "MTOM with XOP". XOP is used as the referencing mechanism in the serialised XML infoset. In theory, the abstract MTOM model could be used with a different referencing mechanism or different container format; also, MTOM could be used over a different transport protocol instead of HTTP. In practice, MTOM is usually used with XOP, MIME and HTTP.
See also
[edit]References
[edit]- ^ Singh, Jayraj; Dhasarathan, Chandramohan (October 2021). "A QoS Metric Approach for Web Service Pertinence for the Cloud". Recent Advances in Computer Science and Communications. 14 (7): 2130–2142. doi:10.2174/2666255813666200102123532. eISSN 2666-2566.
- ^ Mhatre, H. K.; Mehta, B. A.; Jaiswal, A. K. (21 March 2013). Architecture for MTOM based file transfer. 2013 International Conference on Circuits, Power and Computing Technologies. Nagercoil, India: IEEE. p. 1250–1252. doi:10.1109/ICCPCT.2013.6529002. ISBN 978-1-4673-4922-2.
- ^ Jayakumar, S. K. V.; Singh, Jayraj; Joseph, K. Suresh (2014). "Suitable QoS Parameters Survey for Standard Web Services & Web Applications to Understand their Cloud Deployability" (PDF). International Journal of Computational Intelligence and Informatics. 4 (1). ISSN 2349-6363.
