The SOAP Protocol
• As Figure illustrates, SOAP is a transport protocol similar to IIOP for CORBA, ORPC for DCOM, or JRMP for RMI.
SOAP differs from CORBA, RMI, or DCOM in several ways:
• IIOP, ORPC, and JRMP are binary protocols, while SOAP is a text-based protocol that uses XML. Using XML for data encoding makes SOAP easier to debug and easier to read than a binary stream.
• Because SOAP is text-based, it is able to move more easily across firewalls than IIOP, ORPC, or JRMP.
• SOAP is based on XML, which is standards-driven rather than vendor-driven.
• Figure 4.9. The SOAP protocol opens up new options for data exchange across the Web
• The net effect is that SOAP can be picked up by different transport protocols and delivered in different ways.
• For example, when used with HTTP it can be delivered to a Web server; when used over FTP it can deposited directly into a file system; and when used with SMTP it can delivered to a user's mailbox
• Figure 4.10 illustrates that SOAP can be used for direct connection between sender and receiver, or, with the use of messaging middleware,
• SOAP messages can be stored for subsequent delivery and/or broadcast to multiple receivers.
• SOAP extends the Web from server-to-browser to server-to-server interaction.
• Many companies, using SOAP as protocol for exchanging data between established partners is proving a totally satisfactory way to leverage the benefits of XML and the Web.
• All that is required is an agreed-upon schema, either a DTD or an XML Schema, for the XML data being exchanged and a SOAP server capable of handling the incoming XML as it arrives over the Web.
• Details about what kind of schemas to expect and who will check that the XML conforms to the schemas are decided offline by individuals participating in the process.
• On the software side, senders need to be involved in packaging their data in an XML document.
• For those companies already storing data in XML, this should require only minimal effort.
• If the stored XML data is not in the form required by the agreement, an XSL Transformations (XSLT) style sheet can be programmed to automate the transformation.
• As Figure illustrates, SOAP is a transport protocol similar to IIOP for CORBA, ORPC for DCOM, or JRMP for RMI.
SOAP differs from CORBA, RMI, or DCOM in several ways:
• IIOP, ORPC, and JRMP are binary protocols, while SOAP is a text-based protocol that uses XML. Using XML for data encoding makes SOAP easier to debug and easier to read than a binary stream.
• Because SOAP is text-based, it is able to move more easily across firewalls than IIOP, ORPC, or JRMP.
• SOAP is based on XML, which is standards-driven rather than vendor-driven.
• Figure 4.9. The SOAP protocol opens up new options for data exchange across the Web
• The net effect is that SOAP can be picked up by different transport protocols and delivered in different ways.
• For example, when used with HTTP it can be delivered to a Web server; when used over FTP it can deposited directly into a file system; and when used with SMTP it can delivered to a user's mailbox
• Figure 4.10 illustrates that SOAP can be used for direct connection between sender and receiver, or, with the use of messaging middleware,
• SOAP messages can be stored for subsequent delivery and/or broadcast to multiple receivers.
• SOAP extends the Web from server-to-browser to server-to-server interaction.
• Many companies, using SOAP as protocol for exchanging data between established partners is proving a totally satisfactory way to leverage the benefits of XML and the Web.
• All that is required is an agreed-upon schema, either a DTD or an XML Schema, for the XML data being exchanged and a SOAP server capable of handling the incoming XML as it arrives over the Web.
• Details about what kind of schemas to expect and who will check that the XML conforms to the schemas are decided offline by individuals participating in the process.
• On the software side, senders need to be involved in packaging their data in an XML document.
• For those companies already storing data in XML, this should require only minimal effort.
• If the stored XML data is not in the form required by the agreement, an XSL Transformations (XSLT) style sheet can be programmed to automate the transformation.
No comments:
Post a Comment