Clarify tunnel data channel handling in bridge mode

- Updated documentation to clarify that in ALL modes, wsssht handles tunnel control channel messages
- Clarified that in bridge mode specifically, tunnel data channel messages are NOT handled by wsssht
- Instead, raw tunnel data is communicated through stdin/stdout for external processing
- Updated README.md, DOCUMENTATION.md, CHANGELOG.md, and TODO.md with this clarification
- This ensures proper understanding of bridge mode's data handling architecture
parent b624365b
......@@ -18,6 +18,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Real-time JSON status updates during tunnel establishment
- Command processing from stdin with JSON responses
- Structured error reporting and connection status
- **Tunnel control channel messages are handled by wsssht**
- **Tunnel data channel messages are NOT handled by wsssht** - instead, raw data is communicated through stdin/stdout for external processing
- Perfect for programmatic integration and automation
- **Script Mode Implementation**: JSON protocol for scripting
- Periodic status updates (every 30 seconds)
......
......@@ -73,8 +73,11 @@ wsssht --bridge --clientid myclient --wssshd-host example.com
Provides a JSON-based interface for programmatic integration:
- Receives JSON commands from stdin
- Sends JSON status updates and responses to stdout
- **Tunnel control channel messages are handled by wsssht**
- **Tunnel data channel messages are NOT handled by wsssht** - instead, raw data is communicated through stdin/stdout for external processing
- Perfect for integration with other tools and automation frameworks
- Structured error reporting and connection status updates
- External applications can directly handle the data stream
### Script Mode
```bash
......
......@@ -232,6 +232,8 @@ Suppresses all informational output, perfect for scripts and automation.
```
JSON-based communication over stdin/stdout for programmatic use. Receives JSON commands from stdin and sends JSON responses to stdout.
**Important**: In bridge mode, wsssht handles tunnel control channel messages but does NOT handle tunnel data channel messages. Instead, raw tunnel data is communicated through stdin/stdout for external processing by the calling application.
### Script Mode
```bash
./wsssh --script --clientid myclient --wssshd-host example.com
......
......@@ -11,6 +11,8 @@
- Real-time JSON status updates during tunnel establishment
- Command processing from stdin with JSON responses
- Structured error reporting and connection status
- **Tunnel control channel messages are handled by wsssht**
- **Tunnel data channel messages are NOT handled by wsssht** - instead, raw data is communicated through stdin/stdout for external processing
- Perfect for programmatic integration and automation
- [x] **Script Mode Implementation**: JSON protocol for scripting
- Periodic status updates (every 30 seconds)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment