Async-http-client backends removal

sttp client
1

Hello, I see that those backends were recently removed (Remove async-http-client backends by adamw · Pull Request #2373 · softwaremill/sttp · GitHub). Is there any alternative for a CE backend that supports streaming and websockets (WebSocketStreamBackend[IO, Fs2Streams[IO]]). Could that be added to the Http4s backend (Ember)?

I also need multipart support, so it’s not easy to find a backend that does it all :smiley:

Thanks for the recommendations!

Best,
Max

2

I think the default HttpClient-based one is what you’re looking for? fs2 backend — sttp 4 documentation

Or at least I hope so, since it’s the default it should have all the features :slight_smile:

3

I will have a look, thanks!

Otherwise, is the Http4s backend not supporting Websocket a limitation from Ember, or is it just not implemented by the sttp wrapper?

4

Hi Adam, unfortunately using the FS2 backend I run into Streaming multipart bodies are not supported … I don’t believe there are currently any alternative, right?

5

Ah - indeed! The Http4sBackend should work for you just fine, then. It does support multipart streaming bodies.

Could you also create an issue to add support for streaming multipart bodies to the default HttpClient-based backend?

6

Http4sBackend doesn’t support websockets though, so I do need to use both clients, don’t I?

Done! Add support for streaming multipart bodies to the default HttpClient-based backend · Issue #2407 · softwaremill/sttp · GitHub

7

Ah! Well that should be another issue :slight_smile:

Both are doable (adding multipart streaming to HttpClient-backend, and WS to http4s backend), but need some work.

8

Created another ticket for Http4s then Add support for WS to http4s backend · Issue #2409 · softwaremill/sttp · GitHub :slight_smile:

Yes I’m sure… :grimacing: At least back to my original question, I can swap the async http client with the Fs2 one, so there is that!