dave08
02/18/2021, 4:23 PMJoe
02/18/2021, 4:39 PMdave08
02/18/2021, 4:48 PMSubscriptions require a more indepth knoweldge of how the specific server library handles protocols and streaming. Since we can only supportMicronaut has a non-blocking version using Publisher... does that mean that it would be easier to implement? https://docs.micronaut.io/latest/guide/index.html#websocketServerfromPublisher
in this common library, we can not provide any common logic for subscriptions. Therefore you will still need to implement the route and request handling for subscriptions separately if you are not using a provided server implementation.graphql-java
Shane Myrick
02/18/2021, 4:52 PMgraphql-kotlin-spring-server
. It’s just that subscription have to know more about how to handle web sockets and use the specific spring WebSocketSession
to read and send data
https://github.com/ExpediaGroup/graphql-kotlin/tree/master/servers/graphql-kotlin-[…]ain/kotlin/com/expediagroup/graphql/server/spring/subscriptionsgraphql-ws
subprotocol defined by Apollo but even then it is still a lot of code tied to using Jackson and caching the spring specific sessions to send requests back and have custom hooks on top of spring specific eventsJoe
02/18/2021, 4:58 PMdave08
02/18/2021, 5:01 PMJoe
02/18/2021, 5:01 PM