Creating Web Services and Web Clients in Caché
Using the Caché Binary SOAP Format
Caché SOAP support provides an optional proprietary binary SOAP format, which is useful when you send and receive large SOAP messages and want to minimize message size.
As of this release, any Caché web service can receive SOAP requests either in Caché binary SOAP format or in the usual SOAP format. No parameter is needed to enable this behavior. A Caché web client uses binary SOAP format only if it is configured to do so.
This chapter discusses the following:
Caché binary SOAP is carried over HTTP messages as follows:
The message uses the POST method.
The body is a binary representation of objects using a proprietary protocol.
A binary SOAP request includes an HTTP ISCSoap header of the following form:
SOAP sessions are supported. The session information is maintained by using the normal CSP session cookie. However, the SessionCookie
property for SOAP web clients and web services is not supported, because binary SOAP does not use the CSPCHD proprietary SOAP header.
The following example shows a binary SOAP request:
POST /csp/gsop/GSOP.WebServiceBinary.cls HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; Cache;)
Notice that only the SOAP envelope and its contents are affected. The HTTP header is not affected.
Any Caché web service can receive SOAP requests either in Caché binary SOAP format or in the usual SOAP format. If a Caché web service receives a binary request, it sends a binary response. Otherwise, it sends the usual response. No parameter is needed to enable this behavior.
You can extend the WSDL of a web service so that:
The WSDL publicly states that the web service supports the Caché binary SOAP format in addition to the usual SOAP format.
The WSDL includes information on using the Caché binary SOAP format.
This allows any Caché web client to correctly send messages in this format if wanted.
To extend the WSDL of a Caché web service in this way, set the SOAPBINARY
parameter to 1 for the web service.
property of the web client specifies the Caché character set (for example: Unicode, Latin1) of the web service. If the character set of the client machine and service machine are the same, strings are sent RAW; otherwise they are sent encoded as UTF8.
The API for binary SOAP is different from XML SOAP as follows:
© 1997-2019 InterSystems Corporation, Cambridge, MA