<@UL1A5BA2X> Sure. I’m using a unix domain socket ...

# ktor

[spierce7]

@Big Chungus Sure. I’m using a unix domain socket to communicate between a kotlin native binary and a Compose JVM application, to access the camera feed and send it. I’ve found the release version of a kotlin-native application to be more than fast enough on old, low-end hardware, at least on mac. Code posted in thread.

[spierce7]

Create a unix domain socket and wait for connection:

remove("test")
val tcp = aSocket(SelectorManager()).tcp()
val server = tcp.bind(UnixSocketAddress("test"))
println(server.localAddress)

val serverConnection = server.accept()
val serverOutput = serverConnection.openWriteChannel(autoFlush = true)

In your java client connect to the socket:

val tcp = aSocket(SelectorManager()).tcp()
            println("waiting for connection...")
            val clientConnection = tcp.connect(UnixSocketAddress("test"))
            val clientInput = clientConnection.openReadChannel()

Send data from Kotlin native:

serverOutput.writeStringUtf8(imageBase64)
                    serverOutput.writeChar('\n')

[Big Chungus]

What made you choose this over jni?

[spierce7]

JNI has been a nightmare for me previously, of memory strange memory issues. We also kill the process at the end so it’s fresh every time too which gives me some confidence that something screwy hasn’t happened with it.

Can we even use JNI with Kotlin/native [easily]? I’ve never tried. My native app is accessing objc libs, which has a complicated runtime.

[Big Chungus]

I've managed to do it, but can't comment on long term experience. Here's a teaser: https://github.com/mpetuska/fake-kamera/tree/master/jni

[Big Chungus]

https://github.com/mpetuska/fake-kamera/tree/master/app/src/jvmMain/kotlin/jni

[spierce7]

@Big Chungus So you call a Kotlin native library from JVM?

[Big Chungus]

Yes, via jni

[Big Chungus]

And kn binary is embedded in the jar