rathole/docs/out-of-scope.md

# Out of Scope

`rathole` focuses on the forwarding for the NAT traversal, rather than being a all-in-one development tool or a load balancer or a gateway. It's designed to *be used with them*, not *replace them*.

But that doesn't mean it's not useful for other purposes. In the future, more configuration APIs will be added and `rathole` can be used with an external dashboard.

> Make each program do one thing well.

- *Domain based forwarding for HTTP*

  Introducing these kind of features into `rathole` itself ultimately reinvent a nginx. Use nginx to do this and set `rathole` as the upstream. This method achieves better performance as well as flexibility.

- *HTTP Request Logging*

  `rathole` doesn't interference with the application layer traffic. A right place for this kind of stuff is the web server, and a network capture tool.

- *`frp`'s STCP*

  You may want to consider secure tunnels like wireguard or zerotier.

- *P2P hole punching*

  P2P hole punching requires setup on the visitors' side. If that kind of setup is possible, then there are a lot more tools available. `rathole` primarily focuses on NAT traversal by forwarding, which doesn't require any setup for visitors.
feat: init 2021-12-11 13:30:42 +01:00			`# Out of Scope`

docs: add TOC and fix typos (#62) * docs: add TOC * docs: update out-of-scope.md * docs: add some explanation in benchmark.md * docs: update README.md * docs: fix typos 2022-01-05 09:29:43 +01:00			`rathole` focuses on the forwarding for the NAT traversal, rather than being a all-in-one development tool or a load balancer or a gateway. It's designed to be used with them, not replace them.
feat: init 2021-12-11 13:30:42 +01:00
docs: add TOC and fix typos (#62) * docs: add TOC * docs: update out-of-scope.md * docs: add some explanation in benchmark.md * docs: update README.md * docs: fix typos 2022-01-05 09:29:43 +01:00			But that doesn't mean it's not useful for other purposes. In the future, more configuration APIs will be added and `rathole` can be used with an external dashboard.
feat: init 2021-12-11 13:30:42 +01:00
docs: add TOC and fix typos (#62) * docs: add TOC * docs: update out-of-scope.md * docs: add some explanation in benchmark.md * docs: update README.md * docs: fix typos 2022-01-05 09:29:43 +01:00			`> Make each program do one thing well.`

			`- Domain based forwarding for HTTP`

			Introducing these kind of features into `rathole` itself ultimately reinvent a nginx. Use nginx to do this and set `rathole` as the upstream. This method achieves better performance as well as flexibility.

			`- HTTP Request Logging`

			`rathole` doesn't interference with the application layer traffic. A right place for this kind of stuff is the web server, and a network capture tool.

			- `frp`'s STCP
feat: init 2021-12-11 13:30:42 +01:00
			`You may want to consider secure tunnels like wireguard or zerotier.`
docs: add TOC and fix typos (#62) * docs: add TOC * docs: update out-of-scope.md * docs: add some explanation in benchmark.md * docs: update README.md * docs: fix typos 2022-01-05 09:29:43 +01:00
			`- P2P hole punching`

			P2P hole punching requires setup on the visitors' side. If that kind of setup is possible, then there are a lot more tools available. `rathole` primarily focuses on NAT traversal by forwarding, which doesn't require any setup for visitors.