I think that historically, we are good at adding code but not good at
removing code. We add new ways to do things but keep the old. Removal is
more work often forgotten but doing nothing implicitly adds technical debt
henceforth.
With that segue... given that our latest SolrClient implementations are
based on Jetty HttpClient (to support Http2 but should support 1.1?), do we
need the original Apache HttpComponents/HttpClient as well? This is an
honest question... maybe there are subtle reasons they are needed and I
think it would be good as a project that we are clear on them.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
removing code. We add new ways to do things but keep the old. Removal is
more work often forgotten but doing nothing implicitly adds technical debt
henceforth.
With that segue... given that our latest SolrClient implementations are
based on Jetty HttpClient (to support Http2 but should support 1.1?), do we
need the original Apache HttpComponents/HttpClient as well? This is an
honest question... maybe there are subtle reasons they are needed and I
think it would be good as a project that we are clear on them.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley