HTTP Library Replacement

[desp]

Provide a replacement library for the  HTTP package, addressing key concerns voiced about the current implementation.

The replacement should offer marked improvement in several areas, including:

• Convenient interfaces, suitable for both simple and complicated HTTP clients;
• Familiar error reporting mechanisms;
• Solid back-end.
• Liberal usage of  ByteString, for great speedup.

Interested Mentors

• Bryan O'Sullivan < http://www.serpentine.com/blog>
• Dmitry Astapov <dastapov@…>

Interested Students

• Stephen Dolan <stedolan@…>
• Brandon Wilson <bmw.stx@…>

Related work

• network-minihttp, **  http://darcs.imperialviolet.org/minihttp-docs/index.html **  http://hackage.haskell.org/cgi-bin/hackage-scripts/package/network-minihttp

[bos@…]

Don't forget ByteString? goodness.

[desp]

Remembering ByteString? goodness.

[desp]

Added a link to my project webpage.

[nominolo]

The Curl-based library has been implemented.

There's still the possibility of a Haskell-native implementation.

[dons]

A native, bytestring-based HTTP library makes sense now. And Thomas has made initial progress in this area.

[duncan]

I'd also prefer to see a pure haskell implementation (using bytestring). For example I'd want to use it in cabal-install, which has to work on Windows and thus cannot use a curl binding.

[stedolan]

I'd be interesting in doing this project. Could anyone tell me what the "key concerns voiced about the current implementation" are?

[tibbe]

We already have a few of these now, e.g. http-enumerator. It's also requires good knowledge of HTTP and perhaps of more advanced techniques like iteratees.