Late reply to this thread, but we've <implemented>...

# graphql-kotlin

[Joe]

Late reply to this thread, but we've implemented the graphql-ws protocol in our dropwizard/graphql-kotlin based implementation via a compatibility mapping (ie, internally we still "work" in the apollo-ws protocol, but are able to bridge to graphql-ws incoming/outgoing messages). If we wanted to port this over to graphql-kotlin, I can think of a couple ways:
• do a similar compatibility approach in the existing graphql-kotlin/spring implementation
• pull the core execution/state logic into graphql-kotlin-server with an introduced websocket interface (unless we can use javax.websocket with springboot/ktor/etc, but I think they provide their own websocket apis that are not the javax one?) and implement that websocket interface in graphql-kotlin-spring-server (and maybe add a graphql-kotlin-jetty one for our dropwizard etc)
would approach 2 make sense? would want buy in before trying to extract/refactor our impl into that approach