...
Since the volume of messages exchanged between the Windsurfer and external channel, the mechanisms and constraints described below must be implemented.
Type | Mechanism/Constraint | Description |
Retry | Retry strategy for communication failure and in case of specific errors returned in XML response | Windsurfer CRS and external channel will have a retry mechanism in place for communication errors and business error. |
Concurrency | Simultaneous connections per property <= 1 | Property at any given time for updating the ARI events, and allows only one connection per property at a time for receiving booking notifications. |
Timeout | Time out after 60,000 milliseconds (1 minute) | Idle connections (no packets sent by either side) for more than one minute are closed. These should be considered as incomplete and implement a retry strategy to re-send data. |
Character Set | Support for UTF-8 | All messages exchanged must have UTF-8 encoding |
Hotels | Only data related to one hotel can be sent in a single request message | Â |
Date Range | 720 Days | Maximum number of days that a single request message could update must not exceed 720 days |
| Page Properties | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
Summary ARI Message Specification | v1.0Revision
|