[
https://issues.apache.org/jira/browse/SOLR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561067#action_12561067
]
Ryan McKinley commented on SOLR-462:
------------------------------------
I totally agree with why you would not want to use compression for the most
normal use case -- connecting within a LAN or localhost. But If I understand
correctly. From the client side the only difference is that the client says
"hey, I can use compressed data if you give it to me" -- The *server* decides
if compression is ok or not. In any normal case (using solr.war without
editing web.xml and not going through a caching proxy) the results are not
compressed even if the client says it is ok with compressed results.
a trivial point, and I'm happy to go with whatever you think is best....
> Performance related enhancements to Solrj
> -----------------------------------------
>
> Key: SOLR-462
> URL: https://issues.apache.org/jira/browse/SOLR-462
> Project: Solr
> Issue Type: New Feature
> Components: clients - java
> Reporter: Sean Timm
> Assignee: Ryan McKinley
> Fix For: 1.3
>
> Attachments: solrj-SOLR-462.patch
>
>
> Changes to CommonsHttpSolrServer.java to add soTimeout (read timeout),
> connection pool timeout, directive to not follow HTTP redirects, configurable
> retries on NoHttpResponseException, compression, and not creating a new
> HttpClient on each request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
