It's unusual to have Solr be the first point of entry into a service. Usually it's fronted with a web application that has the business logic that knows how to map the request to the search back-end.
Given your further questions, almost anything could work without much trouble: * A standard servlet filter * A search component * A subclass of SearchHandler The search component would probably be easy and most appropriate as you could register it clearly in solr's config file vs. semi-hidden in web.xml ~ David mladen micevic wrote > Thank you David for your quick response. > I was thinking yesterday about my problem. > Caller should not be aware of internals of my Solr configuration (filed > name, operation). > Caller can describe search area with center point and radius and I need to > translate input parameters into Solr query. > Now, I need to have some custom solution in between caller and Solr. > What would be your recommendation how to do it? > Is there any search component that has access to all input parameters and > can create Solr query and pass it to normal search flow defined in search > handler? > Should I create customized implementation of Request Handler? > What would be the best way? > Please advise. > > Thanks > Mladen ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Spatial-filter-in-solr-4-0-Intersects-operation-with-parameters-tp4029034p4029246.html Sent from the Solr - User mailing list archive at Nabble.com.
