I think we can use HttpClient 4 if we really want BTW. Either by creating Classloaders (yuk!), repackaging HTTP client to avoid name conflicts (hopefully much simpler but would require some Maven fiddling) or just use the Abdera version which is still better than anything in java.*
On Mon, Jun 30, 2008 at 9:20 AM, Brian Eaton <[EMAIL PROTECTED]> wrote: > On Sat, Jun 28, 2008 at 3:00 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > The first step here is going to be ensuring that our http facilities are > > extremely robust. The out of the box PHP experience makes good use of > curl, > > which is probably good enough, but the base Java fetcher just plain > sucks. > > Paul Lindner had a great implementation of HttpFetcher using HttpClient > 4. > > At the time, I wanted to use it but we got a version conflict with Abdera > > and gave up (we have our own proprietary solution for use at Google). > > I suspect the normal mode of operation for the Shindig HTTP fetcher > (both PHP and java) will be to use an HTTP proxy server. We should > make it easy to do that, which means good testing and documentation. > > Using a proxy is a good idea because Shindig will be running on your > internal network, but you don't want the Shindig HTTP fetcher to be > able to make requests to your internal network. The easiest way to > avoid that is to set up an HTTP proxy in a DMZ somewhere. >
