Capabilities update request - ALPINEBITS_SEND_HANDSHAKE
It may be useful for the server to be able to ask the client to re-execute the handshake.
A use case is where a server implements a new capability but the client has already done the handshake previously.
It may be easy to implement this functionality by adding "ALPINEBITS_SEND_HANDSHAKE" on page 90 of the 2020-10 document.
These elements must be empty, must have the attribute Type set to 11 (“Advisory”) and must have the mandatory attribute Status with a value chosen among the following, based on the desired complete data set:
- Status = ALPINEBITS_SEND_HANDSHAKE to request the handshake update
- Status = ALPINEBITS_SEND_FREEROOMS to request the full set of free rooms data
- Status = ALPINEBITS_SEND_RATEPLANS to request the full set of rate plans data
- Status = ALPINEBITS_SEND_INVENTORY to request the room configuration
If the server sends more than one of such elements, they must be referred to different data types, meaning that, at the current AlpineBits® version, a server can send up to four different requests: one for each of the above Status values. Upon receiving a response with one or more of these elements, the client should transmit the corresponding data set as soon as possible in any order (see Tips and best practice).
Is anyone interested?