On Tue, Mar 4, 2008 at 5:15 PM, Adam Langley wrote:

On Tue, Mar 4, 2008 at 7:31 AM, Bjorn Bringert wrote:

...

you may want to have a look at the socket abstraction used in the HTTP package:

http://hackage.haskell.org/packages/archive/HTTP/3001.0.4/doc/html/Network-S...

It would be great to get HTTPS support going!

I should have mentioned that I had seen this in the original email. I think the major problem with this interface was that it was written in the time before ByteStrings. Now that we have ByteStrings I think that it makes a lot of sense for networking to use them.

However, it shouldn't be too hard to wrap HsOpenSSL in this interface. I might try this this week. Then HTTPS should Just Work (maybe ;)

There is some (dormant?) work on bringing HTTP into the age of the ByteString. Thomas Schilling (nominolo) might be able to tell you more about it. /B

nominolo:

On 5 mar 2008, at 22.05, Bjorn Bringert wrote:

...

There is some (dormant?) work on bringing HTTP into the age of the ByteString. Thomas Schilling (nominolo) might be able to tell you more about it.

Well, I can say with certainty that I won't have the time nor energy to bring this into a usable state anytime soon (speak: not this year). I think it's unlikely that Jonas will, either. Our work was a quick hack, meant mainly as a proof of concept. Doing it well would require work and more knowledge of the HTTP protocol than I have, ATM. I agree that it would be valuable to the community, but it's not gonna be me.

I wonder, though, what happened to the curl bindings for Haskell? This was a Summer of Code project last year. Also Johan Tibell expressed some interest in getting bytestrings for HTTP.

$ git clone http://code.haskell.org/curl.git :) But really, we want an no-errors bytestring-efficient http of our own.