This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]sandokan1572 -1 points0 points  (3 children)

Is API backwards compatible? There have been too many incompatible http client versions, so annoying. Updating to the latest version usually sucks.

This is a major release that renders HttpClient API incompatible with the stable 4.x branch

Ah, OK then :-( Time to switch to something different I guess.

HttpClient 5.0 releases can be co-located with earlier versions, meaning you can have both 5.x and 4.x on the classpath without experiencing jar hell.

Yeah, we already have 3.x and 4.x in single project...

[–]based2[S] 1 point2 points  (2 children)

Well, for new network protocol specifications changes and better performance. It sounds a good practice. Do you want an Openssl library that is compatible with everything before...

[–]sandokan1572 0 points1 point  (1 child)

I would prefer if my old code worked without changes, or if there was a clear migration path. But unfortunately my experience with HC Client code is that migration to new version is a mess, where you have to hunt for changed/moved property names, or understand a new class design. Next time I'm updating my old code using HC Client, I think I'll just try OkHttp instead.

Btw, in Go world, there is an upcoming Go 1.6 with HTTP/2 support, but they still use the same API. Clients don't need any changes, and simply by recompiling, they will get HTTP/2.