<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 21, 2012, at 11:00 AM, Ray Racine wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I have an HTTPClient library that works for GET, PUT, POST for most use cases where one would use an embedding of a wrapped curl. &nbsp;<div><br></div><div>It understands chunked encoding and "pipes" the de-chunked HTTP stream to a port automatically &nbsp;So for example, you can do a GET of a large file and stream it to disc without reading the entire file into a byte buffer. &nbsp;It also works with HTTPS as well.<div>
<br></div><div>Bad news it is still in unpolished at the API level, with limited scribblings for doc. &nbsp;But I use it quite heavily for AWS REST API integration, web scrapping runs of several hours in duration and it is stable and reasonably fast. &nbsp;</div>
<div><br></div><div><a href="https://github.com/RayRacine/racketlib/tree/master/httpclient">https://github.com/RayRacine/racketlib/tree/master/httpclient</a></div></div></blockquote><div><br></div><div>Wait… don't Racket's built-in libraries already handle all of those cases?</div><div><br></div><div>This is not a rhetorical question: I'm perfectly happy to be wrong, here, but it looks like I can use get-pure-port or post-pure-port to handle these. I guess I assumed that the original poster wanted something that Racket didn't already include, but I could be wrong:&nbsp;</div><div><br></div><div>Yvan, what's your use case look like? Are there things you want to do that, for instance, get-impure-port doesn't already do?</div><div><br></div><div>John</div><div><br></div></div></body></html>