On Tue, Jan 28, 2014 at 2:59 AM, Gabriel Gonzalez <[email protected]>wrote:
> So all the `pipes-parse` work is done and while Renzo is upgrading his > libraries I want to renew discussions about a `pipes`-based HTTP client now > that I think all that the necessary groundwork has been laid by > `pipes-parse` and `pipes-bytestring`. I think you forgot to mention that the `FreeT`-based stuff from `pipes-parse` moved into `pipes-group` (or did you? Perhaps in another email that I missed?). https://github.com/Gabriel439/Haskell-Pipes-Group-Library I've been busy at work, sorry for the delay, I'll try to wrap up everything soon. So, I want to kick off this discussion by saying that Michael Snoyman has > released `conduit`-independent HTTP/HTTPS client libraries called > `http-client` and `http-client-tls`. Things I would like to discuss > include: > > * Should we just reuse `http-client`/`http-client-tls`? Writing a `pipes` > wrapper on top of these would be very quick and painless and I could do it > myself in a couple of days. > Yes, I think this is what we should do in order to get something shipped soon. I played a bit with this code when these libraries were released not so long ago, and it seemed doable. * Should we not use them and reuse something else (like Andrew's proposed > http-streams for `pipes`)? > This would be nice to have, but it will certainly take more time to implement. I suggest we first ship something on top of `http-client` and `http-client-tls`, and then, without the pressure from the community to “ship something soon”, we can spend all the time we want working on this. Regards, Renzo Carbonara. -- You received this message because you are subscribed to the Google Groups "Haskell Pipes" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
