There is one huge advantage of talking to Solr with SolrJ (or any other client that uses the REST API), and that is that you can put an HTTP cache between that and Solr. We get a 75% hit rate on that cache. SOAP is not cacheable in any useful sense.
I designed and implemented the SOAP interface for all the search engines at Verity, so I'm not just guessing about this. wunder On 5/12/08 7:02 AM, "Erik Hatcher" <[EMAIL PROTECTED]> wrote: > > On May 12, 2008, at 9:52 AM, Alexander Ramos Jardim wrote: >> I understood what you said about putting the SOAP at Solr. I agree. >> That's >> not smart. >> Now, I am thinking about the web service talking with an embedded Solr >> server. >> Is that you were talking about? > > Quite pleasantly you don't even really have to code in that level of > detail in any hardcoded way. You can use SolrJ behind a SOAP > interface, and use it with a SolrServer. The implementation of that > can switch between "embedded" (which I'm not even really sure what > that means exactly) or via HTTP the good ol' fashioned way. > > Erik > > >
