Maybe it's worth separating the HTTP parsing from the network management, like Renzo is doing with `pipes-http-message`. However, a priori, I can't see much benefit in trying to come with a shared codebase for managing network connections. The different use cases (server vs client, conduit vs pipes, `http-client` vs `http-streams`) would make it quite hairy. Maybe, we have something working it's easier to see the common patterns and refactor them in a single package.
My 2 cents. -- 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].
