transactions are completed. However, the client not wait for locks on other AsyncRemoteLocalControl clients to be released. If another client is holding a lock, the server shall only act on the remote/local request after the lock is released. The behavior is device dependent. messages are sent normally. AsyncServiceRequest All synchronous messages are left in the input buffer. Normal TCP behavior to prevent buffer overflows takes place. and messages are left in the input buffer. Data, DataEND, Trigger, Error, FatalError, VendorSpecific Data traffic from the server to the client (Data and messages) are sent normally. However, since DataEND incoming synchronous messages are blocked, only responses to operations that were begun before the lock was granted will be generated.
AsyncRemoteLocalControl transactions are completed. However, the client not wait for locks on other clients to be released. If another client is holding a lock, the server shall only act on the remote/local request after the lock is released. The behavior is device dependent. AsyncServiceRequest messages are sent normally. All synchronous messages are left in the input buffer. Normal TCP behavior to prevent buffer overflows takes place. Data, DataEND, Trigger, Error, FatalError, and VendorSpecific messages are left in the input buffer. Data traffic from the server to the client (Data and DataEND messages) are sent normally. However, since incoming synchronous messages are blocked, only responses to operations that were begun before the lock was granted will be generated.
IVI-6.1_HiSLIP-2010-06-08.docx