Transport

Edit pageLast modified: 13 June 2025

Transport layer exists to abstract from the RPC requests logic and focus on delivering and receiving encoded RPC messages in kRPC Protocol. This layer is represented by the KrpcTransport interface. It supports two message formats — string and binary, and depends on which serialization format you choose.

Generic transports

Generally, there are no specific guidelines on how RPC should be set up for different transports, but structures and APIs used to develop integration with Ktor should outline the common approach. You can provide your own transport and even your own fully implemented protocols, while the library will take care of code generation.