1.1.0

[1ureka]

This pull request enhances the WebRTC signaling handshake by introducing a dual-flag mechanism to ensure both peers confirm that their DataChannels are open before proceeding. This improves the reliability of connection establishment by explicitly synchronizing readiness on both sides. Additionally, new logging and error handling have been added for better observability and robustness.

Key changes:

Dual-flag handshake for DataChannel readiness:

• Introduced a new signaling message type (msgTypeReady) to indicate when a peer's DataChannel is open, and updated both host and client flows to wait for this confirmation from the remote peer before finalizing the connection. (internal/signaling/message.go, internal/signaling/signaling.go, internal/signaling/receiver.go, internal/signaling/sender.go) [1] [2] [3] [4] [5] [6] [7] [8] [9]

• Updated the receiver struct to include a peerReady channel and modified the watch method to handle the new ready message type. (internal/signaling/receiver.go) [1] [2]

Improved error handling and timeouts:

• Added a timeout (readyTimeout) when waiting for the peer's ready signal, and improved error handling and logging in both host and client establishment flows to handle negotiation failures and context cancellations more gracefully. (internal/signaling/signaling.go) [1] [2] [3] [4]

Logging enhancements:

• Added debug and info logs for key events, including when the WebSocket server is closed and when negotiation steps succeed or fail. (internal/signaling/ws.go, internal/signaling/signaling.go) [1] [2] [3] [4]