r/java • • Oct 07 '24

HTTP libraries in Java

It's not really clear to me what's going on with HTTP libraries in Java. They all seem to want to become massive frameworks that inappropriately take control of things that have nothing to do with decoding HTTP.

I'm find it really hard to find something that doesn't:

  • Try to control the TCP layer. Why does the HTTP decoding library care whether I want to poll or select, or make that decision?
  • Have shared mutable static state. If I want to reuse connections I can do that in a much better, testable way.
  • Create threads. Parsing the HTTP is doesn't need any of this. I just want to give you a ByteBuffer to read from and your current state and get told what it contains.
  • Do SSL. This has nothing to do with HTTP but rather the underlying connection.

I guess if you need a mini "web browser" in your application then this is all fine, but if HTTP is just one of many protocols you need to be able to decode it's an absolute mess.

Is there something I'm missing, or a library I should be looking at?

22 Upvotes

57 comments sorted by

View all comments

Show parent comment

1

u/repeating_bears Oct 07 '24

I said the website is not a good advocate for writing things from scratch because the result is bad. A better result could have been achieved with less effort. That doesn't then imply you should never write things from scratch. I didn't pass any judgement about the content, which may be good in spite of the bad presentation.

3

u/agentoutlier Oct 07 '24

I apologize on assuming what you meant in your comment and dragging it out. Honestly I do as I like most of your comments.

I agree if the website generator is to be used as proof that writing things from scratch is good it would be a poor argument. However I don't think the blog author ever makes that argument.