Thank you, Guys all for the responces
--
View this message in context:
http://lucene.472066.n3.nabble.com/Call-to-Solr-via-TCP-tp4105932p4107921.html
Sent from the Solr - User mailing list archive at Nabble.com.
gt; simpler solution.
>>
>> Sent from my Windows Phone From: Zwer
>> Sent: 12/10/2013 12:15 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: Call to Solr via TCP
>> Maybe I asked incorrectly.
>>
>>
>> Solr is Web Application, hosted by
. But if you're having a performance or
> infrastructure problem, the group might be able to help you with a far
> simpler solution.
>
> Sent from my Windows Phone From: Zwer
> Sent: 12/10/2013 12:15 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Call to Solr via TCP
>
solr-user@lucene.apache.org
Subject: Re: Call to Solr via TCP
Maybe I asked incorrectly.
Solr is Web Application, hosted by some servlet container and is reachable
via HTTP.
HTTP is an extension of TCP and I would like to know whether exists some
lower way to communicate with application (i.e.
Zwer,
I think it may be a bit dangerous as jetty may start to do some connection
management and expect the client to do so.
However, if you look into http/1.0 you have a little chance that doing simple
http calls is as simple as socket connections.
What could be the reason not to use a decent h
I think it is not possible since Jetty is a HTTP server except jetty is
extensible to support other protocol, that is not a derivation of HTTP
(it supports SPDY, WebSocket).
However, what we do, is putting another layer on top of Solr. Our client
does not directly connect to our Solr, but through
Maybe I asked incorrectly.
Solr is Web Application, hosted by some servlet container and is reachable
via HTTP.
HTTP is an extension of TCP and I would like to know whether exists some
lower way to communicate with application (i.e. Solr) hosted by Jetty?
--
View this message in context:
htt
: I am hosting Solr in Jetty servlet container and just would like to know
: whether exists some way to communicate with Solr through TCP protocol, not
: HTTP?
HTTP ites on top of TCP, so your question doens't
really make much sense to me. Please elaborate on your specific
goal/problem, because