Binary: Difference between revisions
												
				Jump to navigation
				Jump to search
				
(No difference) 
 | 
Latest revision as of 02:24, 4 November 2015
<slideshow style="nobleprog" headingmark="⌘" incmark="…" scaled="true" font="Trebuchet MS" >
- title
 - Web Services Basics For Non-programmers
 - author
 - Pete George (NobleProg Ltd)
 
</slideshow>
Day Two Schedule ⌘
- WSDL
 - Handling Binary Content
 - RESTfull Web Services
 - Other Technologies
 - Conclusion
 
Handling Binary Content ⌘
Learning Objectives
- To understand the need for sending binary data to and from Web services
 - To be aware of the Message Transmission Optimization Mechanism
 
SOAP Messaging ⌘
Parse Whole Message ⌘
Binary Content is the Answer ⌘
Binary Content is the Problem! ⌘
Base64Binary ⌘
- Base64 Encoding scheme
 - Encoding bits into legal characters
 - For relatively small content
 - Included in many SOAP toolkits
 
WS-Attachment ⌘
- Large payloads/binary data as an attachment
 - Stopped work on it 2004
 
MTOM ⌘
- Message Transmission Optimization Mechanism
 - Method for Web services to exchange binary data
 - Replaced WS-Attachment
 - W3C Recommendation
 
MTOM Specification ⌘
Defines MTOM as three features:
- Abstract SOAP Transmission Optimization Feature
 
-Defines exchanging of SOAP messages that contain binary data
- Optimized MIME Multipart/Related Serialization of SOAP Messages
 
-XML-binary Optimized Packaging (XOP) in place of the binary data
-Binary data represented in a MIME container
- HTTP SOAP Transmission Optimization Feature
 
-Defines that MIME + XOP SOAP message sent over HTTP