netty interpreter

[ghostbuster91]

Preliminary roadmap:

• [x] a most basic interpreter, without any special capabilities (such as WebSockets or streaming), passing only the basic testsuite. The supported effect type is scala.concurrent.Future.
• [x] a variant of the backend, which uses an arbitrary effect implementing cats-effect's Async
• [x] streaming support for the cats-effect variant, using fs2
• [ ] multipart support
• [x] websocket support
• [x] zio support
• [x] performance improvements

For inspiration on how to design such a backend, see zio-http and other http servers built on top of netty.

[larochef]

Hello, any idea of when the multipart support could be implemented? I use the netty-sync with ox and would like to stay "direct style", and needed multipart files. I was surprised to get errors when trying it since there is nothing on it on the doc about it.

Since it seems to be mostly implemented, any help would be needed to complete it?

[adamw]

Ah yes, it's been on my TODO list for too long. My current plan is to push this over the finish line early 2025 (January?). There's still some work in @kciesielski PR, so if you'd like to take a look at it, you're more than welcome.

[max-peroch]

Looking forward to see multipart support added to the Netty backend 🥳

[larochef]

Any news on it? I tried to watch it but it seems like the review needs more knowledge on the internals of tapir than I have

[adamw]

@larochef Sorry, we'd love to finish this as well, but we're resource-constrained. For now our immediate plan is finishing sttp client 4, then we'll see where we'll direct our OSS efforts next :)

[markarasev]

Just making some noise because I need multipart support too 😁

[adamw]

With multipart for netty-sync done - closing. If multipart support for netty-future / netty-cats / netty-zio is needed, please vote for this issue: https://github.com/softwaremill/tapir/issues/4851