is the asynchronous web framework for Kotlin created by JetBrains. It is written in Kotlin and its machinery and API is utilizing Kotlin coroutines. It's unopinionated design makes it a very good choice for development of applications composed of many different technologies.
Build configuration
Kilua RPC provides two different modules for Ktor:
kilua-rpc-ktor, which doesn't use dependency injection (DI) and requires manual services registration,
kilua-rpc-ktor-koin, which uses dependency injection framework to access services implementations.
You need to add one of these modules to your project.
val commonMain by getting {
dependencies {
implementation("dev.kilua:kilua-rpc-ktor:$kiluaRpcVersion")
// implementation("dev.kilua:kilua-rpc-ktor-koin:$kiluaRpcVersion")
}
}
Service implementation
Service class
The implementation of the service class comes down to implementing required interface methods.
class AddressService : IAddressService {
override suspend fun getAddressList(search: String?, sort: Sort) {
return listOf()
}
override suspend fun addAddress(address: Address) {
return Address()
}
override suspend fun updateAddress(id: Int, address: Address) {
return Address()
}
override suspend fun deleteAddress(id: Int) {
return false
}
}
You can use @Factory annotation, if you use Koin and koin-annotations to configure dependency injection.
@Factory
class AddressService : IAddressService {
// ...
}
Since Ktor architecture is asynchronous and non-blocking, you should never block a thread in your application code. If you have to use some blocking code (e.g. blocking I/O, JDBC) always use the dedicated coroutine dispatcher.
This function is the application starting point. It's used to initialize and configure application modules and features. Minimal implementation for Kilua RPC integration contains initRpc and applyRoutes function calls. initRpc function should be executed as last.
When using manual service registration, you call initRpc with a lambda function, which binds interfaces with their implementations. Different overloads of registerService function allow injecting server objects into your service classes.
You can use constructor parameters to inject server objects - ApplicationCall and WebSocketServerSession (see chapter) into your service classes. These objects give you access to the application configuration, its state, the current request and the user session (if it is configured).
When using you can choose different security options for different services by calling applyRoutes in different contexts.