We’ve been working on defining our roadmap for Ktor for 2023, and much like we did for 2022, we’d like to share our plans with you and what we have in store. One of the things we’re planning on doing this year is releasing 3.0.0. While major versions generally indicate a breaking change, most of the changes are in regards to API and packaging. In particular We’re going to release the new simplified routing API that we’ve been working on.We’re switching to Tomcat 11, Jetty 11, and upgrading Apache Client to support version 5.We’re extracting the IO functionality into a separate library. T

We’re extremely excited to announce the release of Ktor 2.0. We have been working on this version for approximately one year and happy to finally get it out the door!  Ktor 2.0 introduces many new features, but a major version which means that there are breaking changes, it has allowed us the opportunity to perform some maintenance work and get rid of legacy decisions. Don’t worry though - despite the breaking changes, we’ve tried our best to minimize these and also aid with some tooling that hopefully can help with automated migrations. More on that later though, first let’s take a lo

We’re one month into 2022, and on the Ktor team we’re focusing on finalizing the little that is left from our side on 2.0 and waiting for Kotlin 1.6.20 to be released so as to release 2.0. At the same time, we're planning the next things to be worked on.  As some of you know, we had published our roadmap for 2020-2021 and while we didn’t manage to deliver on everything on it, we weren’t far off. However we also realized that we did in fact bite off more than we could chew.  This led us to try and figure out whether the whole approach to a roadmap where you have a fixed timeline

Exactly one year ago, we announced our plans for the upcoming year. Let's look back and see how we're doing. Focus Areas When we announced the roadmap, we focused on a few key areas that we wanted to improve. While on some of these, we've managed to deliver, on others we're not there yet. We've done a ton of work when it comes to Documentation. Our technical writer Andrey Aksenov deserves a lot of credit for mostly single-handedly not only rewriting many parts of the documentation, but also working on restructuring, and addressing new issues as they come in. Documentation however is a

We're happy to announce the availability of Ktor 1.6.0. This minor release brings with it some new features, deprecations, and of course more bug fixes! Features This release brings a bunch of new functionality to the client, inline with our goals to have client and server parity. Client Progress Support You can now monitor the progress of bytes sent and received in the client, allowing you to for instance provide progress bars in your applications. This was a long-standing issue which has finally been resolved. val response: HttpResponse = client.post("http://localhost:8080/po

As a tooling company, we do realise the importance of providing proper support for the languages and frameworks you use. In the case of Ktor, we started this journey by rewriting support for IntelliJ IDEA Ultimate completely from scratch, and the first step was a new and simplified project wizard, which has already been announced. With the 1.5.3 update, we're improving the options in the wizard, as well as bringing new functionality! New Project Enhancements The Project Wizard comes with two new options: Storing configuration Via the Configuration in dropdown, you can define whether you want

We're very excited to announce the Ktor Early Access Program, where you can get access (thus the name) to things we're working on that won't be available in the currently released version. Often times we'd like to introduce new functionality or APIs that may not be backwards compatible, and get these out to you as soon as they're ready for feedback. That's what our EAP program is about. It's important to understand that while these are not marked as releases, they do go through the same (if not more) tests and checks that our releases go through. We do encourage folks to try EAPs builds, but

We're happy to announce the release of Ktor 1.5.0, which comes with new features, bug fixes, and new docs! Features 1.5.0 is the third and final release for this year, inline with our promise to have three major or minor releases a year, and a minimum of one patch release a month. We're happy to say that so far we've managed to more or less keep this promise, albeit with an ocassional delay at times. In this minor update we have a series of new features including: New Development Mode Ktor provides a series of features targeted at development, such as for instance auto-reload as well as extend

Design in the open Ktor was created as an Open Source project and continues to remain one. During its development, feedback from the community has and continues to be fundamental, and very much appreciated. We'd like to take this to the next step by having all our design decisions in the open. The process will work as follows: Step 1 We create a ticket on YouTrack of type Design, and in it we'll lay out: Description of the issue What it is that we're addressing. Is it a new API? Is it improvements on existing APIs? Is it internal architecture? Current State If applicable, we outline the curren

Often times, in response to an HTTP POST request, we need to provide an ID of a newly created entity. For instance when creating a new record in a database, much like we can have the storage return us the ID, we would like to then provide the same information in the response. There are multiple ways of doing this, but the most common one used is to provide this information as part of the response payload. For instance, with the following request: POST /customer Content-Type: application/json We could respond with: { "id": "5251", "name": "Mary Smi