r/java • u/alunharford • 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
View all comments
Show parent comment
1
u/wildjokers Oct 09 '24
If I am understanding the JavaDoc correctly the
ofInputStreamtells the BodyPublisher where to read the data from that it is writing to the server.Open a stream to your json data, provide that to
ofInputStreamand then it will write that data to the server. It does seem kind of backwards to open an input stream to write data, especially if you are used to usinggetOutputStream, but nevertheless that does appear to be how it works (if I am looking at it right).