Nick Apperley

That example doesn't work. An error message appears after sending the reply on the server side: ``` Illegal data address 0x9C44 in read_input_registers ```

Ktor Client is available for **linuxX64** but not for the other Linux targets (**linuxArm32Hfp**, **linuxArm64** etc) :( .

If Ktor Server was ported to Kotlin Native (supporting the linux targets) would Ktor be suitable for Serverless via [OpenFaaS](https://www.openfaas.com/)? What would the performance footprint for Ktor Server look like...

Is the WIP referring to the Ktor Server implementation? On Tue, 21 Apr 2020 at 22:38, Leonid Stashevsky wrote: > WIP in e5l/cio-common. Yep, the implementation is in progress. >...

@rattrayalex - You might be interested in this [Vert.x example PR](https://github.com/JetBrains/kotlin-examples/pull/57). Vert.x supports hot reloading with Kotlin, and it **works**.

How would this affect [Kotlin Native](https://kotlinlang.org/docs/reference/native-overview.html) projects? In Kotlin Native it is very common to [interop with C libs](https://kotlinlang.org/docs/tutorials/native/interop-with-c.html). For example if Debian is used, and SDL is a dependency...

In consideration of the announcements made at KotlinConf 2019 I have decided that Kotlin 1.3 will be used for the template since it would be trivial to update the template...

Also important that the generated source code follows the official [Kotlin Code Conventions](https://kotlinlang.org/docs/reference/coding-conventions.html).

There is a typo in the description, **Add support for using generated AWS service clients on Kotlin JS targets**. Should be **Kotlin Native** instead of **Kotlin JS**.

Which targets will the Kotlin Native support cover? Does it include **linuxX64**, **linuxArm32Hfp**, and **linuxArm64**?