Looking through the code, it appears that RemoteContentFetcher is only actually used by the samplecontainer code. I'm having a hard time seeing any situation where http retrieval would be a part of the core social-api code (although it could certainly be used to implement the data handlers), so I think that instead of moving the RemoteContentFetcher stuff into common, we should leave it in gadgets and break the dependency on gadgets by having samplecontainer depend on the jakarta http client.
On a related note -- should samplecontainer even be a part of the standard social-api jar? Sure, it should be in the shindig repository, but it seems to me that the odds of someone actually using it on a production site are pretty slim. It seems like a good thing to have as a sub project, much like the various DB-driven implementations that have been floating around. Thoughts?
