Data compression

Data compression is a process that reduces the amount of data needed to transmit a file. This is accomplished via the HTTP/1.1 Accept-Encoding header field. (Note: Data compression is not supported in HTTP/1.0.) Sabre APIs uses the gzip method of data compression. Only the response is compressed following HTTP standard practice. 

Data compression can be helpful but it is not for everyone. The gzip compressed response must be decompressed by the receiving client and the processor time required to perform the decompression may more than offset any response time savings from the smaller message. Customers are strongly encouraged to conduct low volume testing before enabling data compression in production. To assist with testing the Sabre APIs Data Compression Start Up Kit includes a project file for an open source tool named soapUI. (See for details.) 

The data compression start up kit includes two files:

  • Sabre-APIs-Compression-User-Guide.pdf - documentation & user guide (updated Oct 31, 2012)
  • Sabre-APIs-Compression-Test.xml - a soapUI project for benchmark testing (see user guide for details)
Sabre APIs Data Compression Developer's Guide & Sample Project  

Session management overview

Messages that establish and manage connections with the Sabre APIs gateway are referred to as the session management Sabre APIs. (This gateway is also referred to as the USG.) These session management Web services are required to open and close connections (also known as channels) to consume TPFC, orchestrated, open systems, and subscription management Sabre APIs

The session services are used to request connections, obtain authentication and authorization, return connection IDs (in the form of security tokens) to the client, refresh connections, and close connections, ending any allocated Sabre sessions (TAs). They do not request travel-related content from systems and data centers within Sabre, they do not contain business logic, and they do not maintain state. 

These are the session management-related Web services:

  • SessionCreateRQ - Opens a connection to the gateway. You pass your security credentials in the SOAP request and receive a security token in the response.
  • SessionCloseRQ - Closes a connection to the gateway. You pass the security token of the connection you are closing in the request.
  • OTA_PingRQ - Refreshes a connection. You pass the security token of the connection to be refreshed in the request.
Sabre APIs Connection Management: Best Practices and Strategies  

Persistent connections

The Sabre APIs® Persistent Connections document discusses how to use persistent HTTP connections eliminate the need to continuously re-establish connections to Sabre APIs.  Persistent connections are long lived TCP/IP connections that can handle multiple https requests during their life span.  The idea is to maintain a pool of opened connections and use them as needed.  Depending on their geographic location, Sabre APIs clients may see up to a one second reduction in response time per invocation.

Current Production Version: v1.0.0 Sabre APIs Persistent Connections Guide  

Docs Navigation