Re: HTTP and character encodings

On 11/09/2012 19:27, Ben Millwood wrote:

On Tue, Sep 11, 2012 at 6:38 PM, Ganesh Sittampalam wrote:

...

There's http-conduit, which also doesn't support String, but does support https and has a much cleaner interface. If conduit ever made it into the Platform then it would be an obvious choice to replace HTTP; but I still have some faith in lazy IO which is one of the reasons why I put effort into the HTTP package.

As an aside, the major reason I support HTTP over something like http-conduit is the latter's titanic dependency list. I think especially as a dependency of cabal-install that's something of a dealbreaker:

For what it's worth this this isn't my view; I would happily add dependencies to HTTP if they would improve it, although as I'm constrained by what's in the Platform I won't be going wild any time soon. The cabal-install bootstrap process should be improved if the dependencies become prohibitive, e.g. by having hackage generate a complete download bundle. Though honestly, I wonder if HTTP should be in the Platform at all. It certainly wouldn't get in if it were proposed today. On the other hand an http client is an important battery. Ganesh