ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #ktor
Compare CIO, Jetty, Apache, and OkHttp engines in Ktor to pick the best fit for your JVM/Android/iOS/Native project.
Learn how Ktor’s ContentNegotiation plugin, paired with kotlinx.serialization, automatically handles JSON request and response bodies so you can focus on business logic.
Stop manually parsing JSON in Ktor. Learn how to use the ContentNegotiation plugin and kotlinx.serialization to build type-safe, clean REST endpoints.
Learn how to install and configure Ktor's StatusPages plugin to convert exceptions and error statuses into consistent JSON responses, with setup steps, tests, and troubleshooting tips.
For a low-traffic Ktor service, the dominant operational cost is often idle resource consumption: resident memory, parked threads, and event-loop overhead. Ktor offers several server engines—Netty, CIO, Jetty, Tomcat—each with distinct threading and I/O models. Netty relies on event loops and channel pools; CIO is built directly on coroutines and advertises
Handling Write Retries in Ktor Client When using the HttpRequestRetry plugin in Ktor (JVM), the client can be configured to retry requests based on server errors or specific exceptions. However, a critical uncertainty arises when a timeout or connection reset occurs after the server has already processed a write operation but before the client receives the r
Session cookie survival across a Ktor upgrade The goal is to determine whether session state created under an earlier Ktor major release remains valid after the application is upgraded to a newer major release, without requiring users to obtain new cookies. Ktor's default SessionProvider is cookie-based, but its serialization format and configuration can cha
Context Ktor handles HTTP routing and coroutine-based concurrency while Exposed provides the SQL DSL and DAO layer for persistence. Schema evolution in Exposed relies on SchemaUtils.createMissingTablesAndColumns , which performs additive DDL only and lacks a built-in version history or rollback mechanism. Problem When multiple stateless Ktor instances start
When Ktor's client ContentNegotiation plugin is paired with kotlinx.serialization JSON, typed response bodies are deserialized using the installed Json instance and reified type parameters. The integration boundary appears straightforward for a single engine, but the research notes that engine behavior and coroutine suspension are not uniform. Across CIO, Ok
kotlin