Fatal Error Detection and Synchronization Recovery Table Synchronous Fatal Error Message Initiator Message Data Consumer <FatalError><ErrorCode><0><length><message> Accept data and handle Either client or appropriately server Close the connection If initiator is the client, it may Initiator re-open the connection per At any the client or server may encounter a non-recoverable error situation. For instance, the prologue may be incorrect. If either device detects an error condition that is likely to cause the two devices to lose synchronization it shall send the message on the synchronous channel and the asynchronous channel with appropriate FatalError diagnostic information. The IVI Foundation defines the error codes listed in . Error codes from 128-255 inclusive are device defined. The payload be of the specified length and contain a human readable error description expressed in ASCII. A length of zero with no description is legal. If the error is detected by the client, after sending the messages it shall close the HiSLIP connection and FatalError may attempt to re-establish the connection (that is, close both synchronous and asynchronous connections and the connection per section , ). If the error is detected by the server, after sending the messages, it shall close the HiSLIP connection. The FatalError client may re-establish the connection. However the SessionID for the new session will not necessarily relate to the previous SessionID. Note that locks will not be retained and must be re-acquired. Table HiSLIP Defined Fatal Error Codes Code Message Unidentified 0 Poorly formed message header 1 Attempt to use connection without both channels established 2 Invalid Initialization Sequence 3 Server refused connection due to maximum number of clients exceeded 4 Reserved for HiSLIP extensions 5-127 Device defined errors 128-255
Fatal Error Detection and Synchronization Recovery Table Synchronous Fatal Error Message Initiator Message Data Consumer Either client or server <FatalError><ErrorCode><0><length><message> Accept data and handle appropriately Initiator Close the connection If initiator is the client, it may re-open the connection per At any the client or server may encounter a non-recoverable error situation. For instance, the prologue may be incorrect. If either device detects an error condition that is likely to cause the two devices to lose synchronization it shall send the FatalError message on the synchronous channel and the asynchronous channel with appropriate diagnostic information. The IVI Foundation defines the error codes listed in . Error codes from 128-255 inclusive are device defined. The payload be of the specified length and contain a human readable error description expressed in ASCII. A length of zero with no description is legal. If the error is detected by the client, after sending the FatalError messages it shall close the HiSLIP connection and may attempt to re-establish the connection (that is, close both synchronous and asynchronous connections and the connection per section , ). If the error is detected by the server, after sending the FatalError messages, it shall close the HiSLIP connection. The client may re-establish the connection. However the SessionID for the new session will not necessarily relate to the previous SessionID. Note that locks will not be retained and must be re-acquired. Table HiSLIP Defined Fatal Error Codes Code Message 0 Unidentified 1 Poorly formed message header 2 Attempt to use connection without both channels established 3 Invalid Initialization Sequence 4 Server refused connection due to maximum number of clients exceeded 5-127 Reserved for HiSLIP extensions 128-255 Device defined errors