Unirest 5

[ryber]

I'm starting to build out some ideas for Unirest 5 and am open to ideas from the community on which direction we should go. Some of my goals are:

• No change to coordinates or namespaces, there will however be breaking changes to class signatures.
• clean up the interface for multipart form fields with a new builder for advanced options. This will be introduced in Unirest 4 but we will deprecate some of the more eccentric overloads and remove them in 5
• Support streaming mappers
• possibly offer new mapper modules? (protobuf)
• unify and refactor interceptor and metrics to be cleaner and simplified
• Java 25
• look into virtual threads for asynchronous work

Thoughts? Anything else?

[toinouH]

A virtual thread for a thread per request model would be nice.

BUT with virtual thread I advise you like all talks from José Paumard and Allan Bateman to to blocking code. Because when it blocks it detach the thread itself and when the response comes back a thread is assigned again. When you do async task there is no moment to detach so there is no point to use virtual threads.
I really enjoyed this talk https://www.youtube.com/watch?v=962JVfxyuTk since these 2 guys are/were teachers so they explain it in a very simple way :)

[ryber]

You can already set your own Executor in the config. You can set it with a Virtual Thread pool, either customizing it or with Executors.newVirtualThreadPerTaskExecutor()