Peter,
Thank you very much for the reference to the vignette and simple-http
package. simple-http seems to make it quite straightforward, therefore I
will be giving it a go.
Paulo Matos
On 12/04/18 17:28, Peter Schmiedeskamp wrote:
> Darren Newton's simple-http library
>
Darren Newton's simple-http library
(https://github.com/DarrenN/simple-http) vastly eases working with REST
APIs and is very much modeled off of the http client libraries you'd expect
to see in other language ecosystems.
For some quick, useful, and opinionated perspective on REST services, I
On 12/04/18 11:45, Jack Firth wrote:
> I think this is an area where Racket's ecosystem could be significantly
> improved. However, this would probably only be worth the investment for
> those developing on both the client and server side of multiple
> services. Do you have plans to develop your
I think this is an area where Racket's ecosystem could be significantly
improved. However, this would probably only be worth the investment for
those developing on both the client and server side of multiple services.
Do you have plans to develop your own HTTP service APIs in Racket as well?
I can second having used net/url to call simple REST APIs, though
apparently slightly differently than Alex: I typically use
`http-sendrecv/url` to do the data-fetching (rather than `get-pure-port`,
and I build instances of the `url` struct directly rather than using
`format` and `string->url`.
I used the built-in url package (http://docs.racket-lang.org/net/url.html)
from Racket to fetch data from Wunderground weather API and it was simple
enough that I did not feel the need for a separate REST library. I just
used `format` to construct the URL, `get-pure-port` to fetch the data
6 matches
Mail list logo
