We should decide how we want to fit in with java.net.http. There may always be some value in a litesockets based http client to optimize when litesockets is otherwise deeply integrated.
But we may find reuse of some of the data structures from the newly added java.net.http to make it easier to integrate with other libraries and code.
https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/package-summary.html
We may also decide this is a future roadmap item due to java verson compatibility, but something we should evaluate either way.
We should decide how we want to fit in with java.net.http. There may always be some value in a litesockets based http client to optimize when litesockets is otherwise deeply integrated.
But we may find reuse of some of the data structures from the newly added java.net.http to make it easier to integrate with other libraries and code.
https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/package-summary.html
We may also decide this is a future roadmap item due to java verson compatibility, but something we should evaluate either way.