protocol-http versus protocol-httpclient

[Doug Cutting]

I was recently benchmarking fetching at a site with lots of bandwidth, 
and it seemed to me that protocol-http is capable of faster crawling 
than protocol-httpclient.  So I don't think we should discard 
protocol-http just yet.  But there's a lot of duplicate code between 
these, which is difficult to maintain.

I think we should thus merge these, with a configuration parameter 
determining which http backend is used, much like parse-html, which can 
switch between neko and tagsoup.

What do others think?

Doug