![]() ![]() Third, that there is actually only two serious HTTP client libraries in Scala : spray-client and Play! WS.Īnd finally : that you probably want the latter. Second, Github should really display a big red flag over a repo when it has not been updated in over a year. Conclusionįirst, the Google ranking is not an accurate metric to evaluate the quality of a library :) hacktoberfest streaming websocket reactive http-server akka-http http2 http http-client akka. Could really use a bit more visibility outside of the Play! world. The Streaming-first HTTP server/module of Akka. The methods are well named, just use the auto-completion in your favorite IDE and you will find what you’re looking for quickly.ĭiagnostic : good. It is exclusively targeted at people using it inside the Play! framework, even if it’s perfectly usable outside of it. Overall, the API is easy to understand, everything is self-explanatory.Ĭons : the documentation is awful for our use-case. For the current stable version, see sttp 3 on GitHub and its documentation. "no-cache" )) // Requires a 2xx status code. The Scala HTTP client that you always wanted This is the development version of the upcoming sttp client 4. Solution There are many potential solutions to this problem. "some_value", "some_other_parameter" -> "some_other_value" )). You want a Scala HTTP client you can use to make GET request calls. libraryDependencies += "" %% "dispatch-core" % "0.11.3" import dispatch._ import dispatch.Defaults._ // Instantiation of the client // In a real-life application, you would instantiate it once, share it everywhere, // and call h.shutdown() when you're done val h = new Http val requestWithHandler = // Defining the request url ( "" ). First to pop-up in the results, and the doc looks good, that’s a good sign right ? Guess again.
0 Comments
Leave a Reply. |