: > got some follow-up questions about the best way to package up what : > might : > be add-on modules.. is this list the right place to ask?
This list is definitely the right place to start, and As Erik mentioned, this wiki is the first place to look if you are interested in making an Addon... : <http://wiki.apache.org/solr/SolrPlugins> : : You can simply create your code, which I presume would entail a : SolrRequestHandler and a QueryResponseWriter, and distribute it as a : JAR that others could just drop in and run with it. The one hitch here is that the choice of RequestHandler and QueryResponseWriter are driven by URL params, and my skimming of the SRU URL is that SRU has some very specific requirements on what the URL params can/should be ... one way to deal with that might be to write a new Servlet ... but another approach might be to tell people "if you want to use Solr as an SRU service, you must register SruRequestHandler with the name "standard" and you must register the SruResponseWriter with the name "standard" (since those are the defaults Solr uses when the qt and wt params aren't specified) and then http://localhost:8983/solr/select will return your "SRU Explain" page, and be the base URL for all SRU requests. ...but i digress: the point is you can probably impliment everything neccessary for SRU using a custom request handler that does all your query parsing and a custom reponse writer that formats the results appropriately -- onece you have those, then it's just a qustion of how exactly you need to meet the requirements for query params. Ian: I'm not sure how familiar you are with the internals of Solr (or Lucene for that matter) but once you've got the basics of the example app and the tutorial down, take a look the SolrPlugins wiki and the guts of the StandardRequestHandler and it should (hopefully) be clear how you could go about implimenting your own SruRequestHandler. -Hoss
