From efb9dd4e55b21d2def5e58f487d449cd65c66c38 Mon Sep 17 00:00:00 2001 From: mfahampshire Date: Thu, 10 Oct 2024 20:35:46 +0200 Subject: [PATCH] small correction re tcpproxy ffi --- documentation/docs/pages/developers/concepts/messages.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/pages/developers/concepts/messages.mdx b/documentation/docs/pages/developers/concepts/messages.mdx index be839c7766..733fd3addb 100644 --- a/documentation/docs/pages/developers/concepts/messages.mdx +++ b/documentation/docs/pages/developers/concepts/messages.mdx @@ -24,7 +24,7 @@ ReconstructedMessage { This is obviously quite different to e.g. simply being able to read/write from a stream returned from a function call to create a TCP connection, but there are several approaches that developers can take to dealing with this right now. ## Message Abstractions -- Rust/Go/C++ developers can use the `TcpProxy` [stream abstraction](../rust/tcpproxy). +- Rust/Go (and soon C++) developers can use the `TcpProxy` [stream abstraction](../rust/tcpproxy). - Developers who are using Typescript/Javascript can also avoid having to deal directly with messages via using [MixFetch](../typescript/examples/mix-fetch). - As can developers who are bundling and running the standalone [socks5 client](../clients/socks5) using some form of init script. - There will be a seperate pair of binaries coming soon which other developers can use to run as a persistent secondary proxy process based on the [zcash gRPC demo](https://github.com/nymtech/nym-zcash-grpc-demo) codebase, built using the `TcpProxy` abstraction. These will simply expose a `localhost` socket port to pipe traffic to and from in the same way as you would a TCP connection.