So if http4k is targeting java 21 in v6, can we pl...
# http4k
a
So if http4k is targeting java 21 in v6, can we please not drop the Java8HttpClient? It's still incredibly useful on serverless due to its significantly faster cold start time.
d
of course - the Java8 HTTP client is just a wrapper around a URL connection -it's probably badly named TBH...
😁 1
we're not planning on dropping anything - the only reason we dropped the dust templates was that nashhorn was deprecated and removed
m
Rename it to
Java21HttpClient
? 😉
🙃 1
a
TBH I got confused the first time. I thought 8 > no number. But I can't think of a better name for the
JavaHttpClient
. It's name already implies it to be the default choice. Perhaps
Java8HttpClient
could be renamed to
LegacyJavaHttpClient
or something to indicate it's a fallback. Or
HttpsUrlConnectionHttpClient
just like the AWS SDK does
d
It's definitely not legacy - it's more JavaUrlConnectionHttpClient
🤷 1