You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using sttp with tapir/http4s/fs2 to build a websocket server.
My websocket endpoint is described with tapir as:
val instance = endpoint.get
.in(PREFIX)
.out(webSocketBodyRaw(Fs2Streams[IO]))
and my business logic returns a fs2.Pipe[IO, WebSocketFrame, WebSocketFrame]
I have an use case when I would like to send a continuous WebSocketFrame (ie make a stream emit a continuous WebSocketFrame)
which I can't since WebSocketFrame exposes the finalFragment parameter only, not the isContinuation one
isContinuation is exposed in sttp.ws.WebSocket#send which is called by sttp.client3.impl.fs2.Fs2WebSockets#handleThroughPipe
with isContinuation always set to false.
Would that be possible to somehow expose the isContinuation flag when using the web socket with stream pipes ?
Thanks !
Regards,
Sebastien
The text was updated successfully, but these errors were encountered:
Hm I think this should be fixed in Fs2WebSockets.handleThroughPipe itself. If we get a frame with finalFragment = false, it means that all further frames (except this one), until we get a final one, should have isContinuation = true. So this can be computed, doesn't have to be exposed to the user.
Hi,
I'm using sttp with tapir/http4s/fs2 to build a websocket server.
My websocket endpoint is described with tapir as:
and my business logic returns a
fs2.Pipe[IO, WebSocketFrame, WebSocketFrame]
I have an use case when I would like to send a continuous WebSocketFrame (ie make a stream emit a continuous WebSocketFrame)
which I can't since WebSocketFrame exposes the
finalFragment
parameter only, not theisContinuation
oneisContinuation
is exposed insttp.ws.WebSocket#send
which is called bysttp.client3.impl.fs2.Fs2WebSockets#handleThroughPipe
with
isContinuation
always set to false.Would that be possible to somehow expose the
isContinuation
flag when using the web socket with stream pipes ?Thanks !
Regards,
Sebastien
The text was updated successfully, but these errors were encountered: