Elliot Cameron
Elliot Cameron
One way I can think of doing it would be to have the client make a request that doesn't respond immediately. Once the client gets the response, it would generate...
@cgibbard says that they use `QueryT` to get a request-response subscription behavior (running over WebSockets). Another idea is to have the Requester response of type `Event t (Event t Response)`....
@dfordivam That's understandable. The tricky part is that you can only have one websocket connection per port. Requiring two gets complex in other ways, e.g. both can fail separately from...
Maybe that's already easy to do. At the very least it might be good to have an example of that usage in the repo.
Hmm...so when I use `withWebsocketConnection` it gives me a raw websocket that I can use to listen for other events? That won't confuse listeners in the WebSocketMonad?
I'm in WPB - way past bedtime.
@mulderr I like the idea! It makes sense that with websockets the "server/client" should be reversible.
This may be possible by `hold`ing a value on the same event as the WebSocket request event.
We also saw a bewildering issue where HTTP requests from Kiln timed out until we killed the lingering gargoyle+postgres.
@danbornside told me that he has seen this issue when starting gargoyle postgres *after* binding a port (such that it gets inherited). I have not confirmed that this is a...