Accumulate ByteStrings into single result

[emlautarom1]

Accumulate ByteStrings into single result

[emlautarom1]

I found that I can do the following:

-- Client.hs
module Client where

main = do
  let settings = clientSettings 80 "127.0.0.1"
  result <- runTCPClient settings $ \appData -> do
      runConduit $ yield "request" .| appSink appData
      lazy <- runConduit $ appSource appData .| mapC Builder.byteString .| sinkLazyBuilder
      return $ toStrict lazy

  print result

Now I get a single value from runConduit, but this program hangs forever. I assume that it waits forever for more ByteStrings (which will never arrive).

[snoyberg]

In order to make a system like this work, you need to do something like:

• Have the sending side close its send socket to let the receiving side no there's no more data
• Indicate at the beginning of the message how many bytes are coming
• Have some kind of termination signal within the stream

[emlautarom1]

What I ended up doing is the following:

-- Server.hs
module Server where

main = do
  let settings = serverSettings 80 "127.0.0.1"
  runTCPServer settings $ \appData -> do
    void $
      runConduitRes $
        appSource appData .| handler .| appSink appData

handler :: Monad m => ConduitT ByteString ByteString m ()
handler = whenJustM await (const $ yield veryLongString)

-- Client.hs
module Client where

main = do
  let settings = clientSettings 80 "127.0.0.1"
  result <- runTCPClient settings $ \appData -> do
      runConduit $ yield "request" .| appSink appData
      runConduit $ appSource appData .| foldC

  print result

With this, the server will get only the first message with await and then close the connection. I'm not quite satisfied with this solution but it works for my use case. As for the client, I'm not sure if there's a performance degradation on using a single foldC instead of builders, but again, for my use case it seems to be fine.