i don't see a point of having the SitestreamController coupled as part of the Client anymore. I vaguely remember that we wanted to be able to easily make controlstream requests if a Twitter4jSitestreamClient was set up, but it seems reasonable that people may try to use the SitestreamController separate from the Client making the connection to sitestreams. 

Should we just pull that code out, and make the sitestream controller a separate entity?