docs: enhance data read timeout configuration to include connection reuse behavior

Author: yosebyte

docs/en/configuration.md

@@ -125,26 +125,40 @@ Example:
 nodepass "client://server.example.com:10101/127.0.0.1:8080?min=32"
 ```
 
-## Data Read Timeout
-Data read timeout can be set using the URL query parameter `read`, with units in seconds or minutes:
-- `read`: Data read timeout (default: 1 hour)
-  - Value format: integer followed by optional unit (`s` for seconds, `m` for minutes)
-  - Examples: `30s` (30 seconds), `5m` (5 minutes), `1h` (1 hour)
+## Data Read Timeout and Connection Reuse
+
+The `read` parameter controls both data read timeout and connection pool reuse behavior:
+
+- `read`: Data read timeout and connection reuse (default: 0, meaning no timeout and no connection recycling)
+  - Value 0 or omitted: No data read timeout, connections are not recycled to the pool after data transfer completes
+  - Positive integer with time unit: Sets read timeout and enables connection reuse
+    - Value format: integer followed by unit (`s` for seconds, `m` for minutes, `h` for hours)
+    - Examples: `30s` (30 seconds), `5m` (5 minutes), `1h` (1 hour)
+    - If no data is received within the timeout period, the connection is closed
+    - After data transfer completes, the connection is recycled to the pool for reuse
   - Applies to both client and server modes
-  - If no data is received within the timeout period, the connection is closed
 
 Example:
 ```bash
-# Set data read timeout to 5 minutes
+# Set data read timeout to 5 minutes, enable connection reuse
 nodepass "client://server.example.com:10101/127.0.0.1:8080?read=5m"
 
-# Set data read timeout to 30 seconds for fast-response applications
+# Set data read timeout to 30 seconds for fast-response applications, enable connection reuse
 nodepass "client://server.example.com:10101/127.0.0.1:8080?read=30s"
 
-# Set data read timeout to 30 minutes for long-running transfers
-nodepass "client://server.example.com:10101/127.0.0.1:8080?read=30m"
+# Set data read timeout to 1 hour for long-running transfers, enable connection reuse
+nodepass "client://server.example.com:10101/127.0.0.1:8080?read=1h"
+
+# Default behavior: no timeout and no connection recycling (omit read parameter or set to 0)
+nodepass "client://server.example.com:10101/127.0.0.1:8080"
 ```
 
+**Connection Reuse Use Cases:**
+- **HTTP Short Connections**: Set reasonable read timeout and enable connection reuse for frequent short connections to improve pool utilization
+- **Long Connection Optimization**: Set larger timeout values for long-lived connections while avoiding resource waste
+- **Resource Control**: Enable connection recycling by setting timeout in scenarios requiring strict connection lifecycle control
+- **Default Mode**: Use the default no-timeout no-recycling mode for scenarios requiring maximum flexibility
+
 ## Rate Limiting
 NodePass supports bandwidth rate limiting for traffic control through the `rate` parameter. This feature helps prevent network congestion and ensures fair resource allocation across multiple connections.
 
@@ -263,7 +277,7 @@ NodePass allows flexible configuration via URL query parameters. The following t
 | `min`     | Minimum pool capacity | `64`    |   X    |   O    |   X    |
 | `max`     | Maximum pool capacity | `1024`  |   O    |   X    |   X    |
 | `mode`    | Run mode control      | `0`     |   O    |   O    |   X    |
-| `read`    | Data read timeout     | `1h`    |   O    |   O    |   X    |
+| `read`    | Data read timeout and connection reuse | `0` |   O    |   O    |   X    |
 | `rate`    | Bandwidth rate limit  | `0`     |   O    |   O    |   X    |
 | `slot`    | Maximum connection limit | `65536` |   O    |   O    |   X    |
 | `proxy`   | PROXY protocol support| `0`     |   O    |   O    |   X    |

docs/zh/configuration.md

@@ -125,26 +125,40 @@ nodepass "server://0.0.0.0:10101/remote.example.com:8080?mode=2"
 nodepass "client://server.example.com:10101/127.0.0.1:8080?min=32"
 ```
 
-## 数据读取超时
-数据读取超时可以通过URL查询参数`read`设置，单位为秒或分钟：
-- `read`: 数据读取超时时间（默认: 1小时）
-  - 值格式：整数后跟可选单位（`s`表示秒，`m`表示分钟）
-  - 示例：`30s`（30秒），`5m`（5分钟），`1h`（1小时）
+## 数据读取超时与连接重用
+
+`read`参数用于控制数据读取超时时间和连接池连接的重用行为：
+
+- `read`: 数据读取超时时间（默认: 0，表示无超时且不回收连接）
+  - 值为0或省略：无数据读取超时，连接在数据传输完成后不回收到连接池
+  - 正整数加时间单位：设置读取超时时间，并启用连接重用
+    - 值格式：整数后跟单位（`s`表示秒，`m`表示分钟，`h`表示小时）
+    - 示例：`30s`（30秒），`5m`（5分钟），`1h`（1小时）
+    - 如果在超时时间内未接收到数据，连接将被关闭
+    - 数据传输完成后，连接将被回收到连接池供重用
   - 适用于客户端和服务端模式
-  - 如果在超时时间内未接收到数据，连接将被关闭
 
 示例：
 ```bash
-# 设置数据读取超时为5分钟
+# 设置数据读取超时为5分钟，启用连接重用
 nodepass "client://server.example.com:10101/127.0.0.1:8080?read=5m"
 
-# 设置数据读取超时为30秒，适用于快速响应应用
+# 设置数据读取超时为30秒，适用于快速响应应用，启用连接重用
 nodepass "client://server.example.com:10101/127.0.0.1:8080?read=30s"
 
-# 设置数据读取超时为30分钟，适用于长时间传输
-nodepass "client://server.example.com:10101/127.0.0.1:8080?read=30m"
+# 设置数据读取超时为1小时，适用于长时间传输，启用连接重用
+nodepass "client://server.example.com:10101/127.0.0.1:8080?read=1h"
+
+# 默认行为：无超时且不回收连接（省略read参数或设置为0）
+nodepass "client://server.example.com:10101/127.0.0.1:8080"
 ```
 
+**连接重用使用场景：**
+- **HTTP短连接**：为频繁的短连接设置合理的读取超时并启用连接重用，提高连接池利用率
+- **长连接优化**：为长时间保持的连接设置较大的超时值，同时避免资源浪费
+- **资源控制**：在需要严格控制连接生命周期的场景下，通过设置超时启用连接回收
+- **默认模式**：对于需要最大灵活性的场景，使用默认的无超时不回收模式
+
 ## 速率限制
 NodePass支持通过`rate`参数进行带宽速率限制，用于流量控制。此功能有助于防止网络拥塞，确保多个连接间的公平资源分配。
 
@@ -263,7 +277,7 @@ NodePass支持通过URL查询参数进行灵活配置，不同参数在 server
 | `min`     | 最小连接池容量       | `64`      |   X    |   O    |   X    |
 | `max`     | 最大连接池容量       | `1024`    |   O    |   X    |   X    |
 | `mode`    | 运行模式控制         | `0`       |   O    |   O    |   X    |
-| `read`    | 读取超时时间         | `1h`      |   O    |   O    |   X    |
+| `read`    | 数据读取超时与连接重用 | `0`     |   O    |   O    |   X    |
 | `rate`    | 带宽速率限制         | `0`       |   O    |   O    |   X    |
 | `slot`    | 最大连接数限制       | `65536`   |   O    |   O    |   X    |
 | `proxy`   | PROXY协议支持        | `0`       |   O    |   O    |   X    |