If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:SOAP
BoxMatrix >> Lexicon >> Network-Protocols >> SOAP | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
Protocol
Protocol: | SOAP | Wiki | Freetz | IPPF | whmf | AVM | Web |
Short for: | Simple Object Access Protocol (formerly) | ||||||
Location: | Lexicon >> Network-Protocols | ||||||
Weblinks: | Wikipedia.int - Wikipedia.de - W3C-SOAP-1.2 | ||||||
Description: | XML based messaging protocol |
Goto: Examples - FRITZ!OS - SMW-Browser
Details
SOAP is a universal XML based messaging protocol used in many contexts today.
It was initially introduced as a XML Remote Procedure Call
format which explains what it's used for.
Today SOAP is a wrapper format for exchanging data between many Webservices and their clients.
A SOAP message consists of up to 5 blocks:
- XML header
- SOAP envelop
- SOAP header (optional)
- SOAP body
- SOAP fault (optional)
If SOAP is used with HTTP / HTTPS an additional SOAPAction:
HTTP-Header can be added.
This can be used to filter SOAP requests without having to interpret the request or response body.
Examples
wsdd uses SOAP messages which consist of a XML header and a SOAP envelope containing a SOAP header and a SOAP body.
The envelope references the XML namespaces used in the SOAP message.
<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:pnpx="http://schemas.microsoft.com/windows/pnpx/2005/10" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07" xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"> <soap:Header> <wsa:To> urn:schemas-xmlsoap-org:ws:2005:04:discovery </wsa:To> <wsa:Action> http://schemas.xmlsoap.org/ws/2005/04/discovery/Hello </wsa:Action> <wsa:MessageID> urn:uuid:%s </wsa:MessageID> <wsd:AppSequence InstanceId="%u" MessageNumber="%u" SequenceId="urn:uuid:%s" /> </soap:Header> <soap:Body> <wsd:Hello> <wsa:EndpointReference> <wsa:Address> urn:uuid:%s </wsa:Address> </wsa:EndpointReference> <wsd:XAddrs> http://%s/%s </wsd:XAddrs> <wsd:MetadataVersion> 1 </wsd:MetadataVersion> </wsd:Hello> </soap:Body> </soap:Envelope>
The SOAP header defines the target address, message id and action to perform. The SOAP body contains the payload data,
which is action specific.
FRITZ!OS
The following FRITZ!OS parts use SOAP:
- libavmupnp.so, libavmupnpbig.so
- libcmapi.so
- libewnwnet.so
- libjuisclient.so
- wsdd
- libtr069.so
- tr064cgi
- tr064.lua