Fabio
01/24/2022, 1:17 AMmbonnin
01/24/2022, 8:15 AMNetworkTransport
API instead of WsProtocol
?mbonnin
01/24/2022, 8:16 AMWebSocketNetworkTransport
main goal is to multiplex subscription over a single WebSocketConnection but I understand this multiplexing doesn't exist with SSE because each subscriptions either has:
• its own TCP connection (HTTP1)
• or uses multiplexing at the HTTP layer (HTTP2)mbonnin
01/24/2022, 8:18 AMrquestUuid
or do any of the serializing all messages in the messages
channelmbonnin
01/24/2022, 8:43 AMmbonnin
01/24/2022, 8:45 AMtext/event-stream
that sends messages delimited by an extra newline:
data: message1
data: message2
data: message3 is a
data: multi-line message
data: message4
?Fabio
01/24/2022, 10:23 PM<https://github.com/enisdenjo/graphql-sse>
And while you can open an SSE per subscription that's not the path we're taking, it's akin to what's described in the middle of the above doc. Btw we'll use HTTP1.
And you got the bulk of SSE right. We're planning to use SSE id:
to help with demultiplexing and finding the correct "destination" of a particular data:
piecembonnin
01/24/2022, 10:58 PMHaving aforementioned limitations in mind, a "single connection mode" is proposed. In this mode, a single established SSE connection transmits all results from the server while separate HTTP requests dictate the behaviour.
mbonnin
01/24/2022, 10:59 PMmbonnin
01/24/2022, 11:01 PMWebsocketNetworkTransport
logic for demultiplexing will be handymbonnin
01/24/2022, 11:03 PMFabio
01/25/2022, 12:11 AMHi 👋 . Quick question: would it make sense to use theI definitely need a new transport. I also went out of my way to also use WsProtocol, in the hopes of reusing something, but so far nothing good came out of it.API instead ofNetworkTransport
?WsProtocol
Fabio
01/25/2022, 12:13 AMFabio
01/25/2022, 12:14 AMapollo-kotlin
.mbonnin
01/25/2022, 8:11 AMmbonnin
02/08/2022, 9:06 AM