Hm, we can't do this quite as easily, since we now lose track of the pipelining if we only give the client the underlying conduit (which will be the same for a pipelined connection).  I think this needs to be functorized out of Cohttp -- doing that now.