View source for Binary

{{Cat|Web Services Basics For Non-programmers|08}}

<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 ⌘=
[[File:Binary 1.png|600px]]

=Parse Whole Message ⌘=
[[File:Binary 2.png|600px]]

=Binary Content is the Answer ⌘=
[[File:Binary 3.png|600px]]

=Binary Content is the Problem! ⌘=
[[File:Binary 4.png|600px]]

=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
=Quiz – No Prizes! No Pressure! ⌘=
[[File:Binary 5.png|600px]]