Jeena 47faae81e5 Add standalone POC comparing WebRTC DataChannel vs Socket.IO ... Self-contained test under poc-webrtc/ that does not touch the game. Spins up an Express + WebSocket signaling + node-datachannel server alongside a Socket.IO server, serves a simple browser client that runs the same game-like traffic pattern (14Hz worldUpdates, input events, ping/pong) over either transport based on a URL flag. Captures per-session stats to a JSONL file and ships an analyze.js that prints a per-(transport, phase) summary of RTT percentiles, receive rate, and seq-gap counts so the TCP-vs-UDP-style comparison becomes quantitative rather than eyeball. Confirms node-datachannel installs and works on this platform and that the dual-channel (reliable + unreliable) pattern is feasible to maintain — both prerequisites for the real integration.		2026-05-11 00:38:01 +00:00
..
client.js	Add standalone POC comparing WebRTC DataChannel vs Socket.IO	2026-05-11 00:38:01 +00:00
common.js	Add standalone POC comparing WebRTC DataChannel vs Socket.IO	2026-05-11 00:38:01 +00:00
index.html	Add standalone POC comparing WebRTC DataChannel vs Socket.IO	2026-05-11 00:38:01 +00:00
socketio-client.js	Add standalone POC comparing WebRTC DataChannel vs Socket.IO	2026-05-11 00:38:01 +00:00