Replies: 5 comments 11 replies
-
@Thihup I would be fine with you incubating this. What about ....
What do you think? |
Beta Was this translation helpful? Give feedback.
-
Might also be good to keep an eye out on what Helidon is doing. Dmitry announced something like this on Twitter a short while ago. Maybe we can work together in some way. |
Beta Was this translation helpful? Give feedback.
-
This is really interesting indeed. However, I hope that the core Piranha can keep Java 17 as a baseline for a long while, even after the next Java LTS is released. Even with 17 there are still some issues. For example, AWS Lambda doesn't support Java 17 out of the box and a custom runtime is required to run Piranha on AWS Lambda. |
Beta Was this translation helpful? Give feedback.
-
HttpServers are really pluggable in Piranha. We can already run on JDK HttpServer, Grizzly and Netty. |
Beta Was this translation helpful? Give feedback.
-
FYI https://twitter.com/gunnarmorling/status/1536613918491168769 |
Beta Was this translation helpful? Give feedback.
-
Check if we could create an incubating HTTP implementation using Virtual Threads.
Right now, it is only available for JDK 19+, so we should not make it in the default Piranha package because it would require features that are not in the current LTS (JDK 17).
Maybe in the next LTS, we could use the HTTP implementation using Virtual Threads by default.
(One thing to note is: will we keep using our own HTTP implementation to run/pass the TCK? If so, we'll need to implement the HTTP/2 - and possible HTTP/3 in the future - by hand)
Beta Was this translation helpful? Give feedback.
All reactions