Hi @pabl0rg.  I'm not too familiar with HTTP4k but it should be possible, although it would require abstracting out the HTTP/WebSocket transport code, which isn't something I'd contemplated previously. Does HTTP4k have significant advantages over Ktor, or is it more that you're locked into it?

The nice thing about http4k is it's all just functions. For that reason, it should be easy to switch to ktor, with the main disadvantage being losing easy testability. I'll give it a try, though. Thanks!

That would be good - I don't think I've spoken to @dave so not sure if he is familiar with Kweb. Kweb uses Ktor for HTTP/HTTPS transport and WebSocket transport. It would be great if that could be abstracted out, provided that it didn't complicate Kweb's simpler use-cases.

yeah, it might help adoption if people can try making a screen or two with it in an existing project.

The Ktor integration is mostly contained within the

Kweb

class: https://github.com/kwebio/kweb-core/blob/master/src/main/kotlin/kweb/Kweb.kt

yeah - we do know about kweb, but haven't really used it TBH. But all the bits seem to be there to make it workable into an http4k integration. you would be locked into Jetty because that's the only http4k engine that supports websockets at the moment. All of the current KWeb code would need to be ported into creating a

PolyHandler

which could then be converted using

asServer(Jetty(...))

. However, for partially applying it to individual pages as per @pabl0rg’s idea you would need to do something funky with the routing to mix in the kweb routes with the standard http4k ones. PBasically you'd need to migrate all of the w/s stuff from Kweb.kt into an http4k and then you could mix in