Re: Serving remote lucene client - RMI vs HTTP

2007-07-16 Thread Ryan McKinley
customizable Solr really is (rather the ease with which we can do it). Also Solr doesn't support queryFilter out of the box (Hossman: there's nothing to stop a solr request handler from using QueryFilter's if they want). How much extra work is it? out of the box, solr supports query filters.

Re: Serving remote lucene client - RMI vs HTTP

2007-07-16 Thread kumarlimbu
serve dynamic pages but all the searching will take place on the >> > >> search >> > >> application. Web application will send search parameters >> > to the search >> > >> application and after searching, it will send back the results to >&g

Re: Serving remote lucene client - RMI vs HTTP

2007-07-16 Thread Erick Erickson
ur needs. Unfortunately our >> team is not >> familiar with RMI and so we don't know if there will be any issues >> with it >> during implementation. >> Advantage of using simple GET/POST is we have more control which >> searcher >> app to use and when. An im

RE: Serving remote lucene client - RMI vs HTTP

2007-07-16 Thread Ard Schrijvers
x27;t know if there will be any issues >> with it >> during implementation. >> Advantage of using simple GET/POST is we have more control which >> searcher >> app to use and when. An important criteria for us is to disable >> searching >> from the searcher

Re: Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread Chris Hostetter
: And our final queries sent to lucene are quite complicated. This is because : we need to confirm to a lot of criteria (some are set by users and some are : internal logics). I don't think we can simplify our queries. in my experience, your queries can always be made simpler by making your index

Re: Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread kumarlimbu
s very >> important >> for us. Is there anyway in RMI to inform the web (client) >> application that a >> particular server is unavailable (due to index being updated). >> >> We would also like to know if anybody has implemented lucene >> searching in a >

Re: Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread Grant Ingersoll
ion that a particular server is unavailable (due to index being updated). We would also like to know if anybody has implemented lucene searching in a similar fashion. Thanks for your help. Kumar Limbu -- View this message in context: http://www.nabble.com/Serving-remote- lucene-client---RMI-vs-HTTP

Re: Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread qi wu
- From: "kumarlimbu" <[EMAIL PROTECTED]> To: Sent: Monday, July 16, 2007 10:10 AM Subject: Serving remote lucene client - RMI vs HTTP > > Hi Everyone, > > We are using lucene,nutch and spring framework to create a specialized > search engine. Due to growing tra

Re: Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread Ken Krugler
Hi Everyone, We are using lucene,nutch and spring framework to create a specialized search engine. Due to growing traffic we are trying to scale. By doing some tests we found out that the bottle neck was lucene search. We used some heavy traffic simulation and logged the time taken by each portio

Serving remote lucene client - RMI vs HTTP

2007-07-15 Thread kumarlimbu
nybody has implemented lucene searching in a similar fashion. Thanks for your help. Kumar Limbu -- View this message in context: http://www.nabble.com/Serving-remote-lucene-client---RMI-vs-HTTP-tf4084167.html#a11608209 Sent from the Lucene - Java Users mailing list archive at Nabble.com.