The XML Select Web Service provides all of the functionality of the XML Select product without the need for the client to host the XML Select content and transactions. The benefits of using the XML Select Web Service are that updates to the Services happen instantaneously and that Galileo is responsible for hosting and access to the content.
Exception handling should be provided for the different types of errors that can occur in any XML Select transaction: HostApplicationError and TransactionErrorCode.
gzip encoding lets you modify the SOAP Header to enable gzip compression in the response.
The XML Select Web Service uses eight methods to handle identification, sessioning, Host Access Profiles (HAPs), cruise transactions, and XML submission.
|
Method |
Requires |
Description |
|
HAP |
Returns an XML document with the user ID, pseudo city code, and host that is being accessed. | |
|
HAP, XML, Filter |
Allows users to send a single sessionless structured data transaction within a single web call. | |
|
HAP, XML, Filter |
Allows users to send multiple sessionless structured data transactions within a single web service call. Note: If you are submitting multiple, simultaneous, sessionless XML requests, use MultiSubmitXml rather than multiple SubmitXml requests. MultiSubmitXml returns the same response, but uses the server resources more efficiently and has better performance. | |
|
HAP |
Signs the user on and initializes a session token to be used with sessioned transactions. | |
|
Token |
Signs the user off and releases the session token. | |
|
HAP, Filter |
Allows access to cruise transactions. | |
|
Token, XML, Filter |
Allows users to send a single sessioned structured data transaction within a single web call. | |
|
Token, String |
Allows users to send terminal transactions using a session. |