Update readme

Author: JoeTurki

examples/data-channels-whip-whep-like/README.md

@@ -1,40 +1,66 @@
-# whip-whep
-whip-whep demonstrates using WHIP and WHEP with Pion. Since WHIP+WHEP is standardized signaling you can publish via tools like OBS and GStreamer.
-You can then watch it in sub-second time from your browser, or pull the video back into OBS and GStreamer via WHEP.
+# whip-whep-like
 
-Further details about the why and how of WHIP+WHEP are below the instructions.
+This example demonstrates a WHIP/WHEP-like implementation using Pion WebRTC with DataChannel support for real-time chat.
+
+**Note:** This is similar to but not exactly WHIP/WHEP, as the official WHIP/WHEP specifications focus on media streaming only and do not include DataChannel support. This example extends the WHIP/WHEP pattern to demonstrate peer-to-peer chat functionality with automatic username assignment and message broadcasting.
+
+Key features:
+- **Real-time chat** with WebRTC DataChannels
+- **Automatic username generation** - Each user gets a unique random username (e.g., SneakyBear46)
+- **Message broadcasting** - All connected users receive messages from everyone else
+- **WHIP/WHEP-like signaling** - Simple HTTP-based signaling for easy integration
+
+Further details about WHIP+WHEP and the WebRTC DataChannel implementation are below the instructions.
 
 ## Instructions
 
-### Download whip-whep
+### Download the example
 
 This example requires you to clone the repo since it is serving static HTML.
 
 ```
 git clone https://github.com/pion/webrtc.git
-cd webrtc/examples/whip-whep
+cd webrtc/examples/data-channels-whip-whep-like
 ```
 
-### Run whip-whep
+### Run the server
 Execute `go run *.go`
 
-### Publish
+### Connect and chat
 
-You can publish via an tool that supports WHIP or via your browser. To publish via your browser open [http://localhost:8080](http://localhost:8080), and press publish.
+1. Open [http://localhost:8080](http://localhost:8080) in your browser
+2. Click "Publish" or "Subscribe" to establish a DataChannel connection
+3. You'll be assigned a random username (e.g., "SneakyBear46")
+4. Type a message and click "Send Message" to broadcast to all connected users
+5. Open multiple tabs/windows to test multi-user chat
 
-To publish via OBS set `Service` to `WHIP` and `Server` to `http://localhost:8080/whip`. The `Bearer Token` can be whatever value you like.
+Congrats, you have used Pion WebRTC! Now start building something cool
 
+## Why WHIP/WHEP for signaling?
 
-### Subscribe
+This example uses a WHIP/WHEP-like signaling approach where an Offer is uploaded via HTTP and the server responds with an Answer. This simple API contract makes it easy to integrate WebRTC into web applications.
 
-Once you have started publishing open [http://localhost:8080](http://localhost:8080) and press the subscribe button. You can now view your video you published via
-OBS or your browser.
+**Difference from standard WHIP/WHEP:** The official WHIP/WHEP specifications are designed for media streaming (audio/video) only. This example extends that pattern to include DataChannel support for real-time chat functionality.
 
-Congrats, you have used Pion WebRTC! Now start building something cool
+## Implementation details
+
+### Username generation
+Each connected user is automatically assigned a unique username combining:
+- An adjective (e.g., Sneaky, Brave, Quick)
+- An animal noun (e.g., Bear, Fox, Eagle)
+- A random number (0-999)
+
+This creates usernames like "SneakyBear46" or "BraveFox789".
 
-## Why WHIP/WHEP?
+### Message broadcasting
+The server maintains a broadcast hub that:
+- Registers all connected DataChannels
+- Associates each channel with a unique username
+- Broadcasts every message to all connected users (including the sender)
+- Automatically cleans up when users disconnect
 
-WHIP/WHEP mandates that a Offer is uploaded via HTTP. The server responds with a Answer. With this strong API contract WebRTC support can be added to tools like OBS.
+### Thread safety
+All hub operations use `sync.RWMutex` to ensure thread-safe access to the connection map and username mapping.
 
 For more info on WHIP/WHEP specification, feel free to read some of these great resources:
 - https://webrtchacks.com/webrtc-cracks-the-whip-on-obs/