paulrbrown+haskell-cafe:

On Thu, Mar 27, 2008 at 12:08 PM, John Goerzen wrote:

...

* Bjorn's String-based HTTP It eats RAM. Does not appear to read data lazily, returns a String, and may have a memory leak as well. Does not appear to be suited for anything except very small file downloads.

Do you know why it's eating RAM? With the issue with open sockets resolved (I know, I have to send that patch to Bjorn...), I haven't had observable stability or leaking issues. I'm using it to hit JSON/XML services like Twitter, del.icio.us, Google reader, etc.

Laziness here is a bit of a mixed bag, since if you're too lazy, you'll try to read the stream after it's long gone. (Principle of Least Surprise)

We do need a real (HTTPS, support for encoding, possibility to be lazy) HTTP client library, and a binding for libcurl may be the short path.

And we have a curl binding, already in wide use. http://code.haskell.org/curl.git/ a release to hackage is imminent.

Hi, On Fri, Mar 28, 2008 at 6:42 AM, John Goerzen wrote:

On 2008-03-28, Don Stewart wrote:

...

paulrbrown+haskell-cafe:

...

And we have a curl binding, already in wide use.

http://code.haskell.org/curl.git/

a release to hackage is imminent.

Do you mean this?

http://hackage.haskell.org/cgi-bin/hackage-scripts/package/curl-1.3.1

Looks like it's not quite as current as your Git repo.

Is this surprising? Hackage is not a revision control system. The curl package on hackage is a fairly recent version of the git repo. -Iavor

On Thursday 27 March 2008 04:38:21 pm Paul Brown wrote:

On Thu, Mar 27, 2008 at 12:08 PM, John Goerzen wrote:

...

* Bjorn's String-based HTTP It eats RAM. Does not appear to read data lazily, returns a String, and may have a memory leak as well. Does not appear to be suited for anything except very small file downloads.

Do you know why it's eating RAM? With the issue with open sockets

It appears to be insufficient laziness. You'll probably never notice it because you're only downloading small files. Trying to download a 20MB file resulted in 500MB RAM usage for me before I killed it. -- John

On 2008-03-27, Adam Langley wrote:

On Thu, Mar 27, 2008 at 12:08 PM, John Goerzen wrote:

...

* network-minihttp

Doesn't appear to actually be very useful as a client.

Also, as far as I have been able to deduce, none of these have built-in support for https (SSL) URLs.

The client doesn't do a lot, but I don't know what you would want from a client. Email me a list of use cases and ;)

You know, it actually looks very nice to me. I don't know what I was looking at before, but I've poked around at your sources a bit and I like what I see. The fact that I can get a result as a lazy ByteString is nice. Your Source type is an interesting approach, too. -- John