From cb45cdf7eb38fd4623f093bdb6e1e1d05adf97eb Mon Sep 17 00:00:00 2001 From: mmmray <142015632+mmmray@users.noreply.github.com> Date: Mon, 1 Jul 2024 21:27:33 -0500 Subject: [PATCH] Make global transport settings deprecated (english) --- docs/en/config/transport.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/en/config/transport.md b/docs/en/config/transport.md index f2f4a6c79..54d62adb9 100644 --- a/docs/en/config/transport.md +++ b/docs/en/config/transport.md @@ -6,13 +6,16 @@ Transports specify how to achieve stable data transmission. Both ends of a conne Transport configuration consists of two parts: -1. Global config ([TransportObject](#transportobject)) +1. ~~Global config ([TransportObject](#transportobject)) (deprecated)~~ 2. Local config ([StreamSettingsObject](#streamsettingsobject)). - When locally configured, you can specify how each inbound or outbound connection is transmitted individually. - Server inbounds and client outbounds often need to use the same transport protocol. When a transport protocol is specified without local configs, the transport will fall back to global transport configs. -## TransportObject +
+Global configuration (deprecated) + +## TransportObject (deprecated) The `TransportObject` corresponds to the `transport` property in the config root. @@ -68,6 +71,8 @@ Configures Domain Socket connections. Configures SplitHTTP connections. +
+ ## StreamSettingsObject `StreamSettingsObject` corresponds to the `streamSettings` property in the inbound or outbound config. Each inbound or outbound can be configured with different transports and can use `streamSettings` to specify local configs.