Couldn't you just add the websocket object as a receiver so you could write onConnect instead of ws.onConnect in the lambda?

it's written in java for interoperability 🤔

Ahhhh, that might cause issues then yes. Sorry, I thought it was Kotlin only

but that would be nicer, i agree

yeah, maybe i should have said

There could still be kotlin-only versions that are receivers instead, as an idea!

Just in case someone is looking for the same solution, next step will be have it using persistence

none spring FTW!!!

lol

not specifically made for Kotlin, but I've used Dropwizard with Kotlin without any issues for a couple of projects

@m If you're looking for pure kotlin - you can find a list on https://kotlin.link/?q=web - in which case Ktor (as wasabi) is the best known (maintained by @orangy), myself and @s4nchez maintain http4k . On the Java-initiated side, Spark has kotlin bindings now, and that's very popular, as does vert-X and jooby.

There are a few more, but I'm not sure how many of them are actually used in production vs being prototypes

@dave thanks, how is ktor compared with spring and spark? even though ktor is pure kotlin, kotlin users seem to use spring and spark more than ktor.

well, you could say that spring is so pervasive that you'd find developers using it as a default option for everything 🙂

then again, php. 😆

are there any non-jetbrain companies using ktor?

i'm planning on using it

can't say i'm a company though

i suspect that @orangy will be able to tell you. from the http4k side, it's in prod use at my current client (a global publisher) serving ~20mrpd. there's also a couple of investment banks that I know of using it in prod - but we don't really have an "Adopter" list, so we've no idea 🙂

thanks!

Yeah, #ktor is evolving pretty good and is almost feature complete for v1. It is being used in production, not only at JetBrains. It’s 100% Kotlin, have idiomatic APIs, http://ktor.io for (incomplete) documentation and all other goodies of an Open Source project. One of its major benefits is extensive use of Kotlin coroutines, which makes web services asynchronous and at the same time source code easy to comprehend.

There's also kovert that works decently well, but it's really a framework you can put on top of others (e.g., initial host framework is Vert.x which is also good)

vert.x is pretty much dead right? in the US at least..?

Huh?

was listening to a friend of mine tell me about a project he was on

where the microservices were built on vert.x a few years ago

he was saying no one is using it in the US, it failed to get any traction

i guess it's dead in the same sense that anything except spring and javaee is dead

@codeslubber can you elaborate why do you think so ?

there is slight a difference between it’s not mainstream and it’s not dead 🙂