Unify the HTTP Apis

[arjantijms]

Jakarta EE 10 has two competing APIs for HTTP handling; one provided by Servlet, the other by REST.

This is highly undesirable. Both users and other vendors need to learn / support two largely distinct APIs.
AB#51

[hantsy]

I hope there is a new standard API to unite common network operations, like Spring ServerExchange(adapt for different protocols, Http, WebSocket, RSocket, gRPC, etc) and DataBuffer(similar to ByteBuffer and Netty ByteBuf), use reactive/async by default.

Publisher<ServerRequest> request = exchange.getRequest();
Publisher<ServerResponse> request = exchange.getResponse();

Switch to blocking/sync by a simple method.

ServerRequest request = exchange.getRequest().toBlocking(an optional timeout);
ServerResponse request = exchange.getResponse().toBlocking();

(also create a client like this)

For Jakarta EE 11, we can consider virtual thread and construct concurrency from the scratch. And refactor the current Servlet, Rest spec, and also requires a context propagate(support sync and async automatically, recognized by all specs, esp CDI, EL, etc) to pass request state through different contexts without explicit copy etc.

[hantsy]

This is highly undesirable. Both users and other vendors need to learn / support two largely distinct APIs.

Maybe define a new specification, and refactor Rest and Servlet/Pages/Faces to use it as base.

[hantsy]

@edburns Why we need Azure to manage jakarta issues, https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo ?

[hantsy]

Helidon4 web server is rewritten from scratched, and embraces VT. The new Http Apis can be inspired from the existing work.