Tags API (3) , Conference (8) , Dispatcher (2) , Geneva (1) , Go (6) , Guardian (1) , I2P (1) , IETF (7) , IPC (3) , Localization (1) , MASQUE (1) , Minecruft (1) , Multipath (1) , Obfs4 (1) , Obfuscation (2) , Operator (3) , PTIM (2) , PTIM2020 (7) , PTSpec (2) , Rhizome (1) , Shapeshifter (1) , Spec (2) , Specification (3) , Swift (1) , TCP (1) , UMD (1) , Virtual (8) , conference (1) , create (2) , developer (41) , grants (12) , implement (32) , implementation (9) , library (2) , marionette (1) , meeting (18) , minecruft (1) , repository (1) , research (3) , shapeshifter (1) , software (1) , specification (1) , transport (14) , video (1) , virtual (19) , Archives by Date
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
August 2021
July 2021
March 2021
December 2020
October 2020
September 2020
January 2020
December 2019
March 2019
February 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
July 2017
June 2017
May 2017

subscribe via RSS

How to Use Pluggable Transports in Your Application

Updated:

Also by Operator Foundation’s Brandon Wiley is a new guide for application developers interested in implementing pluggable transports using the Go API.

Applications that are also written in Go can use transports implementing the PT 2.0 Go API directly, bypassing the IPC layer. This decreases the complexity of integration, as well as the performance overhead of running the transports in a separate process. Additionally, the Operator Foundation provides a tool called Shapeshifter Dispatcher, which wraps transports implementing the PT 2.0 Go API to provide the IPC layer. This allows applications written in programming languages other than Go to use these transports with no additional development cost.

Read How to Use Pluggables Transports in Your Application for a complete walkthrough for adding pluggable transports.