aws

http://status.aws.amazon.com/ https://www.expeditedssl.com/aws-in-plain-english
kenny 2019-06-14T17:46:25.033300Z

Is there a reason aws-api is on an old version of com.cognitect/http-client?

ghadi 2019-06-14T19:19:18.033700Z

@kenny we talked this morning about http-client in general

ghadi 2019-06-14T19:19:26.034Z

is the old version causing you pain?

kenny 2019-06-14T19:20:32.035400Z

Yes - the old version of jetty aws-api uses is not compatible with the latest version of jetty.

kenny 2019-06-14T19:21:05.036700Z

I explicitly updated http-client to the latest and it fixes the conflict. Seems like aws-api should update to the latest as well.

ghadi 2019-06-14T19:21:32.037300Z

we can't do a newer http-client than what datomic uses yet

ghadi 2019-06-14T19:22:08.038200Z

another way to handle is to explicitly depend on latest Jetty, I think that http-client is compatible with it

ghadi 2019-06-14T19:22:36.038500Z

we're considering a model for BYOHttpClient too

ghadi 2019-06-14T19:22:44.038700Z

still early

ghadi 2019-06-14T19:23:43.039Z

@kenny what are you using that pulls in Jetty 9.4?

kenny 2019-06-14T19:24:30.040Z

Using a http client that doesn’t use jetty (i.e. http-kit) would be great. Ring pulls in 9.4.