Trivial Description
While working on GUACAMOLE-313, it was discovered that the "tee" implementation of guac_socket (created through a call to guac_socket_tee()) only actually locks/unlocks the primary socket when sending instructions. This means that instructions which are manually sent along the secondary socket may overlap with instructions written through the tee socket, resulting in protocol errors.
Both primary and secondary sockets should be threadsafe relative to instruction writes on the tee socket.
Attachments
Issue Links
- relates to
-
GUACAMOLE-313 Allow input events within session recording
-
- Resolved
-