Fork me on GitHub
Matthew Davidson (kingmob)04:09:22

I have a question for users of the Aleph HTTP client as it relates to clj-http compatibility. When the response body is empty, clj-http returns nil, while aleph currently returns an empty InputStream. On the one hand, clj-http compatibility is explicitly the goal of Aleph’s HTTP client, and incompatibility is usually treated as a bug. On the other hand, we’re concerned about the impact of switching to returning nil. Would this change heavily affect you? React with an emoji to answer. > it wouldn’t affect me, or it’s not a big deal, go ahead and change it > it would affect me, please leave the current behavior as is